[SOLVED] FH_DATE_PAST_20XX - Spamassassin bug - incorrect tagging from Jan 1, 2010 on

[Yann2]

Hello, it seems there is a rule in Spamassassin with a weight of 2 affecting all emails with a sent date of 2010 and later.

More information: Rules/FH_DATE_PAST_20XX - Spamassassin Wiki

Seems my Zimbra spammassassin had this rule, I applied the proposed configuration workaround.

[phoenix]

Hello, it seems there is a rule in Spamassassin with a weight of 2 affecting all emails with a sent date of 2010 and later.

More information: Rules/FH_DATE_PAST_20XX - Spamassassin Wiki

Seems my Zimbra spammassassin had this rule, I applied the proposed configuration workaround.

Can you file a bug report in bugzilla?

[Yann2]

Bug 43766 – FH_DATE_PAST_20XX - Spamassassin incorrect tagging from today

[phoenix]

Bug 43766 – FH_DATE_PAST_20XX - Spamassassin incorrect tagging from today

Thanks very much and Happy New Year to you.

[Yann2]

Thanks, to you and to the whole Zimbra team too

[WolfyPDX]

There's a serious bug in SpamAssassin that is rewarding 3+ points to every email starting today (01/01/2010). The problem is the rule FH_DATE_PAST_20XX which is intended to flag mail from the future as spam. This is likely to create a lot of false positives in mail received on Zimbra systems. The short term solution is to edit /opt/zimbra/conf/spamassassin/50_scores.cf and 0 out the FH_DATE_PAST_20XX rule, then restart.

[WolfyPDX]

Ah, I see somebody else has reported this too.

[deepblue]

Hi all,

I stumbled upon the same thing. In Zimbra 6.0.3 it is enough to put

score FH_DATE_PAST_20XX 0.0

in salocal.cf(.in) and restart amavis. But this does not do the job in Zimbra 5.0.x.

I had to edit /opt/zimbra/conf/spamassassin/72_active.cf and I modified line 543 to be:

header   FH_DATE_PAST_20XX      Date =~ /20[2-9][0-9]/ [if-unset: 2006]

Regards
Thomas

[raj]

ok spent few hours updating all zimbra nodes

orignal discussion for this bug is at
https://issues.apache.org/SpamAssass...ug.cgi?id=6269

* it mentiones that if you edit by hand as work-around it will not stick if you run sa-udpate, but zimbra dont package sa-update too YET so i guess it should be ok till new version is released

Raj

[ajayrockrock]

I stumbled upon the same thing. In Zimbra 6.0.3 it is enough to put

score FH_DATE_PAST_20XX 0.0

in salocal.cf(.in) and restart amavis.

restarting amavis with zmamavisctl stop/start, didn't do the trick for me. I had to shut it down (zmcontrol stop) and bring it back up for zimbra to rewrite the config files. Once I did the full restart, the conf/salocal.cf file was rewritten with the new rule.