There was a notification from ReturnPath about a 2010 bug in SpamAssassin a few hours ago:
Description
A bug was discovered in the default configuration of SpamAssassin that caused all email sent as of 2010 to trigger a 3.4 point addition to the SpamAssassin score with a description of ?The date is grossly in the future.?
Impact
1)
All Spam Filter Check results for SpamAssassin will include an additional 3.4 points in the score and the description ?The date is grossly in the future.?
This will continue until the fix has been implemented and is representative of other servers running SpamAssassin that have not implemented the fix.
2)
Any emails sent as of January 1, 2010 to servers running SpamAssassin before the fix was made available, and to any servers running SpamAssassin that have not implemented the fix, will experience a higher than normal SpamAssassin score. This might impact delivery for messages where the score increase is significant enough to put the email's score above a filtering threshold.
There is a rule in SpamAssassin that will hit on any message with a date of 2010 or later and add a whopping 3.2 points, which will cause many messages to be incorrectly marked as spam.
John May at Point In Space Internet Solutions provided this fix:
The fix is to edit your local config file at /private/etc/mail/spamassassin/local.cf and add the line:
score FH_DATE_PAST_20XX 0.0
will disable the bug until it's fixed.
Or, you can edit the rule source itself: go to /usr/share/spamassassin/72_active.cf and find the line:
header FH_DATE_PAST_20XX Date =~ /20[1-9][0-9]/ [if-unset: 2006]
And replace it with:
header FH_DATE_PAST_20XX Date =~ /20[2-9][0-9]/ [if-unset: 2006]