Bug 181651 - Filters: "If filter matches, stop processing here" is sometimes ignored for X-Envelope-To
Summary: Filters: "If filter matches, stop processing here" is sometimes ignored for X...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-23 10:50 UTC by Graham P Davis
Modified: 2015-04-12 10:01 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Graham P Davis 2009-01-23 10:50:26 UTC
Version:            (using KDE 3.5.10)
OS:                Linux
Installed from:    SuSE RPMs

I have several addresses for which I wish to avoid spam filtering on incoming mail. I have 17 filters, one for each address, which are of the following form.

In the general tab, I have the criteria "match any of the following" and these are the three "To/CC/X-Envelope-To contains [my-email-address]". The filter action is set to move into a suitable folder for that address. 

In the advanced tab, I have set "apply the filter to incoming messages from all accounts", "apply this filter on manual filtering" and "if this filter matches, stop processing here".

For some filter rules, this works perfectly. For others, if the address is in "X-Envelope-To", the "stop processing" is ignored and the list of filters continues to be processed, finally arriving at the spam processing. If the message passes the spam filter successfully, the earlier part of the filter is actioned and the message is filed in the correct folder. The rules always work - so far - if the address is in "To" or "CC".

In one filter rule, I have experimented with using a single filter of "anywhere in headers" but this mis-behaves in exactly the same way.

I'm not sure whether this bug has appeared recently due to a code change or because I have added more filters and gone beyond an internal program limit.

The filters have been correctly recognized - else why would the filing have worked - so why hasn't the "stop processing" command worked?
Comment 1 Graham P Davis 2012-03-06 09:43:41 UTC
I have checked the filter log and have concluded that the address filter is failing to find the address in my address book. I've added the address from the failed e-mail just in case the original was incorrect but a subsequent run failed to find it.

Anyway, I've given up on kmail as version 4.8 is unusable. All it has done is add more bugs to those that were there in 4.4. So you can do what you like with this.
Comment 2 Laurent Montel 2015-04-12 10:01:24 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.