Summary: | Fix and improve filtering support | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Thomas McGuire <mcguire> |
Component: | misc | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | unnamedrambler |
Priority: | HI | Keywords: | akonadi-ports-regression |
Version: | 1.99.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Bug Depends on: | |||
Bug Blocks: | 223438 |
Description
Thomas McGuire
2010-01-19 20:37:39 UTC
(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 |