Summary: | Multiple actions in one filter not applied correctly | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Nick Leverton <nick> |
Component: | Mail Filter Agent | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | montel, peter |
Priority: | NOR | ||
Version: | 4.9 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Export of all filters |
Description
Nick Leverton
2012-11-26 10:09:47 UTC
Still an issue in 4.9.97 RC2. Still an issue in 4.10, unfortunately. paste your filter settings (just filter where there is the problem) thanks Hi Laurent, my problematic filter is: Filter Criteria: Match all Subject: contains: sometext Subject: does not contain: Re: Filter Actions: Mark As: Read Move Into Folder: DIMAPaccount/Deleted Items Advanced Options: Apply to incoming: from all Apply on manual filtering "Match all" invalidate other check => Subject: contains: sometext and "Subject: does not contain: Re:" is not looked at. => this filter match all message. => all message will move in directory but it 's not your bug. Created attachment 77838 [details]
Export of all filters
I've just realised kmail offers an "export filter" button so I'm attaching the results of that. Since the above I've added spam filters using the Spam wizard. These are in the export also. Now I am getting two copies of each detected spam in the JunkMail folder. There is one which has passed through spamc and been wrapped, and this is correctly marked read. There is also one copy which has no spamc headers or wrapping and this is not marked read. Apologies for drip feeding comments; I've just realised that the message duplication (one marked read and one still unread, both in the destination mailbox of the move) is also applying to the original filter now as of 4.10.1. In 4.10.0 there was only one still-unread copy being moved to the destination mailbox. Seems to be fixed in 4.11.2, thankyou. |