Bug 331180

Summary: Mail filtering does not work always with akonadi-server-1.11.0 and kmail-4.12.2
Product: [Frameworks and Libraries] Akonadi Reporter: Tobias Leupold <tl>
Component: Mail Filter AgentAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: major CC: grzesiekw
Priority: NOR    
Version: 1.11.0   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Tobias Leupold 2014-02-16 10:58:04 UTC 
Sometimes, but not always, mail filtering does not work at all with recent versions of kmail and akonadi-server, at least with akonadi-server-1.11.0 and kmail-4.12.2. When I boot my machine and kmail starts automatically, most of the time, no filtering is done at all and all emails go to the inbox (which is really annoying as I use a lot of filters and have to put them into their destination folders by hand).

The mail filter protocol is simply empty. Nothing is done. I don't know if this only affects POP3 accounts – at least, I only use POP3.

Sometimes, closing kmail, logging out of KDE, restarting kdm, logging back in and restarting kmail helps and filtering starts working again.

I really don't know how to debug this. No error message is displayed, no log file written. It simply doesn't work and sometimes starts to work again for a reason I don't know.

I had the same behavior with kmail-4.12.1, but with 4.12.2, it happens much more often.

This is really annoying. I'd really like to help to track this down if someone would tell me HOW I can find out why this happens.

Reproducible: Sometimes
Comment 1 grzesiekw 2014-12-15 10:34:41 UTC 
I have the same problem with KDE 4.14.3 and akonadi 1.13.0 (x86_64). I use only IMAP account for filtering.
After restarting akonadi-server it works for some time.
Comment 2 Denis Kurz 2017-06-23 19:56:50 UTC 
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-02-01 09:50:13 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.