SpamAssassin Rule: FH_DATE_PAST_20XX Problem Fix Needed Please

[vickibellamy]

Hi we have been experiencing a major problem with emails in that they are being considered spam, even though email addresses are whitelisted. The following description appears:


0.5 RCVD_IN_PBL ***********RBL: Received via a relay in Spamhaus PBL
***************************[86.133.194.71 listed in zen.spamhaus.org]
1.6 RCVD_IN_SORBS_DUL *****RBL: SORBS: sent directly from dynamic IP address
***************************[86.133.194.71 listed in dnsbl.sorbs.net]
3.2 HELO_LH_HOME **********HELO_LH_HOME
3.4 FH_DATE_PAST_20XX *****The date is grossly in the future.
0.0 HTML_MESSAGE **********BODY: HTML included in message
0.1 RDNS_DYNAMIC **********Delivered to trusted network by host with
***************************dynamic-looking rDNS
-1.2 AWL *******************AWL: From: address is in the auto white-list

We have researched into the description reading 3.4 FH_DATE_PAST_20XX The date is grossly in the future.
and it seems apparent this is a bug where all mail from start of 2010 are getting an extra 3.4
points so are seen as spam: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6269

Is anyone able to help us fix the bug, we are using Plesk 8.6 on linux on virtuozzo container.

Many thanks,

Vicki

 

[sinbad]

Hope this helps...

2010-01-01: Y2K10 Rule Bug - Update Your Rules Now!

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.

 

[calderwood]

Found the fix at Bugzilla for SpamAssassin error

This fixed the problem

Run: sa-update

Then check that it updated:
grep FH_DATE_PAST_20XX /var/lib/spamassassin/3.002005/updates_spamassassin_org/72_active.cf

Response should be:
##{ FH_DATE_PAST_20XX
header FH_DATE_PAST_20XX Date =~ /20[2-9][0-9]/ [if-unset: 2006]
describe FH_DATE_PAST_20XX The date is grossly in the future.
##} FH_DATE_PAST_20XX

If not, manually change the 20/[1-9] into 20/[2-9]