Versions 3.2 of SpamAssassin have (until very recently) a bug in their rules which would mark mails dated 2010 (this year) as being spam.
The reason for this is that a rule exists which would add an additional score of 3.2 to mails with a date set to 2010, because when the rule was created, the date would be in the very far future. Of course, this is no longer the case.
The bug was already discovered in 2008, and resolved in the SpamAssassin repositories, but was not backported to 3.2 until 2010-01-01, when the issue was discovered by Mike Cardwell, a developer in the UK.
Spam nowadays is a real pain. While linux users are fairly safe against most common viiri and spyware, spam mail affects everyone.
While there are many spamfilters out there, I've found that only one is pretty effective, on the long run as well. This guide provides a solution to implementing this filter into KMail for local scanning, filtering and retraining.
A working KMail configuration for scanning and retraining spamfilter with POP3 accounts (IMAP is not supported because mail doesn't really get "downloaded").A DSPAM 3.6.x using the hash_drv, with training data stored in the user's homedi ...
read more
