Right now, the automatic filtering filters everything that emits an itemAdded() signal. This will not work very well: Items will get filtered when for the first time synchronizing a maildir or an IMAP account, when items are copied around and under other circumstances where items should not be filtered. Also, the filtering should not block the KMail GUI. That is the most hated bug in KDE, and we promised to fix this for Akonadi, advertising this as one of the key benefits of Akonadi. We should deliver the promise. There are two options to approach this: One is to bend the existing filtering framework in KMail into submission, and the other one is to use the new filtering framework for Akonadi from last year's summer of code. Filtering should have all the features that KMail 1 had. That is all rules and actions, but also features like excluding accounts from automatic filtering on new mail, applying filters to outgoing or sent messages and so on (have a look in the old configure filters dialog)
(In reply to comment #0) > and under other circumstances where items should not be filtered. So, under what circumstances should items be filtered? > and the other one is to use the new > filtering framework for Akonadi from last year's summer of code. This is the filtering framework correct? http://websvn.kde.org/trunk/playground/pim/akonadi/filter/ How read for prime time is it?
> So, under what circumstances should items be filtered? Only when checking mail with POP3/IMAP. Not at the initial sync, and also not on every ItemCreateJob. Basically we would need a flag for ItemCreateJob, and take care to not filter on the initial sync > This is the filtering framework correct? > http://websvn.kde.org/trunk/playground/pim/akonadi/filter/ > > How read for prime time is it? I'd say it still needs a fair amount of work, not something that could be done before the KMail 2.0 release.
The mail filter agent is in master now