Version: (using KDE KDE 3.5.7)
Installed from: Ubuntu Packages
After upgrading to Kubuntu KDE 3.5.7 packages (containing kmail 1.9.7) mail filters don't work reliably anymore.
For example, I have the following:
but even though I have plenty of mails that spamassassin did flag as spam, it doesn't match.
Spamassassin actually adds a X-Spam-Status header, not X-Spam-Flag.
Can you check if maybe this was your error?
I tried with X-Spam-Status contains 'yes' and that works for me.
Actually, that filter worked just fine before the upgrade!
Here's a header excerpt from a message marked as spam:
X-Spam-Checker-Version: SpamAssassin 3.1.7-deb (2006-10-05) on buz-t60.lan
X-Spam-Status: Yes, hits=16.6 required=7.5 tests=BAYES_99,EXTRA_MPART_TYPE,
TVD_FW_GRAPHIC_ID1,UNPARSEABLE_RELAY autolearn=no version=3.1.7-deb
I can't figure out why it suddenly stopped working. I think some other filters still trigger, but don't move messages like they should.
Going back to 1.9.6 as shipped in Kubuntu Feisty lets the very same filters work again, BTW.
Hmm, seems like spamassassin only adds the X-Spam-Flag header to mails which are spam, but the X-Spam-Status header to every mail.
Anyway, I added you filter to my kmailrc (without the check-mail part though) and tested. It works like it should. In KMail 1.9.7.
Are you perhaps using IMAP?
Does the filter work if you use "mark as important" instead of "move to trash" as action?
I think I have recieved this bug report in debian also. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425739
This is not related to Spamassassin/X-Spam.
Since 3.5.7 nearly all my mails are not filtered anymore, too.
See also bug 126182.
I agree, it also happens on other filters, so it is NOT specific on
SpamAssassin. Some filters still trigger, but subsequently fail to move the
mails to the intended destination.
I will close this as a duplicate of bug 126182 then. Plenty of people who upgraded to 1.9.7 have already commented there, and it seems to be the same problem as here. Maybe the new version only triggers that bug more often.
*** This bug has been marked as a duplicate of 126182 ***