SpamAssasin Troubles For Senders 2

SpamAssasin has announced that there is a bug in the software that could be adding a score of up to 3.6  for any email dated 2010.  As email senders, we are now going to be reliant on SpamAssasin operators to go in and make this update.  Be aware that if you see some decreased numbers that this may be a contributing factor.  In SpamAssasin’s defense, I am sure they couldn’t have imagined that in 2010, we would still be sending ADVERTISEMENTS in email.  I think the use of “Y2K10 Bug” is pretty clever.  Is it possible that thousands of consultants just heard a ding in their ears?  Carefully stepping down from my soapbox before I get started, here’s the information from SpamAssasin.

Y2K10 Rule Bug – Update Your Rules Now!

2010-01-01:

Versions of the FH_DATE_PAST_20XX rule released with versions of Apache SpamAssassin 3.2.0 thru 3.2.5 will trigger on most mail with a Date header that includes the year 2010 or later.  The rule will add a score of up to 3.6 towards the spam classification of all email.  You should take corrective action immediately; there are two easy ways to correct the problem:

  • If your system is configured to use sa-update run sa-update now.  An update is available that will correct the rule.  No further action is necessary (other than restarting spamd or any service that uses SpamAssassin directly).
  • Add “score FH_DATE_PAST_20XX 0” without the quotes to the end of your local.cf file to disable the rule.

If you require help updating your rules to correct this issue you are encouraged to ask for assistance on the Apache SpamAssassin Users’ list.  Users’ mailing list info is here.

On behalf of the Apache SpamAssassin project I apologize for this error and the grief it may have caused you.

Regards,

Daryl C. W. O’Shea

VP, Apache SpamAssassin

2 thoughts on “SpamAssasin Troubles For Senders

  1. Pingback: TheWebBlend.com

  2. Pingback: uberVU - social comments

Leave a Reply