www.ninjahdev.com

The recent spamassasin bug reared it's ugly head today when we found an old Mdaemon server (that uses Spamassassin as its detection engine) that was wrongly scoring emails as spam.

The error in the logs was "3.2 FH_DATE_PAST_20XX The date is grossly in the future."

The solution (besides paying for updates), is to edit the ruleset.

C:\MDaemon\SpamAssassin\rules\local.cf

Add the following line score

FH_DATE_PAST_20XX 0.0

Restart Spam Engine