The mail dispatcher agent stops working after some random (longer) time, leading to mails sitting in the outbox until you restart the mail dispatcher in akonadiconsole. Reproducible: Always Steps to Reproduce: 1. log in to KDE 2. use your KDE session for several hours without relogging 3. try to send a mail Actual Results: mail sits in outbox until forever Expected Results: Mail should actually be sent
this bug is still present in 4.9.2 and annoys me to no end. possible duplicates: https://bugs.kde.org/show_bug.cgi?id=306203 https://bugs.kde.org/show_bug.cgi?id=288605
This happens to me as well, the system has been running for quite some time and mail dispatcher agent just silently (!) stops working until restart. This is a major bug, I always noticed it only after several days The mail dispatcher agent had this error: The name org.freedesktop.Akonadi.Resource.akonadi_maildispatcher_agent was not provided by any .service files But this does not seem to be the cause, because it is showing that now after restarting and I can send emails just fine right now I agree with Mathias that the other two are duplicates, could somebody please give us hints how to track this down? karsten@thermoskanne:~> akonadictl --version Akonadi 1.9.0 karsten@thermoskanne:~> kmail --version Qt: 4.8.4 KDE: 4.10.00 KMail: 4.10
would be nice if this got some attention... still around in 4.10.1 :(
I still have this bug in Arch with 4.10.5 ... I am wondering why no one does comment on this ... is it not happening for most people? ... or is the number of users productivly using Kmail so small that there is not to much interest? ... or is it considered not to be important? ... or is this no akonadi but a kmail bug? To get things going it would be nice to hear from someone who's developing on this. thx for reading, piedro
And there's already one less user because of this problem - as I switched back to thunderbird that I already let down hoping kmail2 will be as cool as kmail1.
(In reply to comment #4) > I still have this bug in Arch with 4.10.5 ... I am wondering why no one does > comment on this ... is it not happening for most people? ... or is the > number of users productivly using Kmail so small that there is not to much > interest? ... or is it considered not to be important? ... or is this no > akonadi but a kmail bug? > > To get things going it would be nice to hear from someone who's developing > on this. > > thx for reading, > piedro Perhaps you can give infos no ? "Ok it doesn't work" great for me it works.
I run KDE on Arch, it's version 4.10.5. This bug is not random: Anytime I leave my box running for more than a day (this is an estimate) the akonadi agent has to be restarted. And, by the way, this is true for: - mail dipatcher agent - mail filter agent (filtering always stops at a certain runtime) - local notes (for kjots: it stops showing the notes altogether and has to be restarted to work again) - ... there may be more but these are the agents I use mostly use Years ago I had a similar problem. That had to do with the missing entry "wait_timeout=31536000" in the mysql.conf. But now I checked in the folder "~/.local/share/akonadi" - the file "mysql.conf is present and has the above entry. thx for reading, piedro
Now I installed a new system (ARch linux, KDE 4.10.5) and the mail dispatcher agent still stops working after a long uptime. "Restart agent" with akonadi console immediately sends out mail and after that the mail dispatcher works again for quite some time ... What info exactly do you need? I am happy to provide ... thx for reading, piedro
*** This bug has been confirmed by popular vote. ***
I have the same bug. I'm using KDE 4.11.3 :s
Is this fixed? Can the bug be removed?
it didn't happen for quite some time, but what still happens is that mail is being sent but still keeps sitting in my local outbox after it has been sent. the only way to be sure is to look in the sent mail folder for the account.
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.