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

[jrefl5]

My fix was to change 27_active.cf in /opt/zimbra/conf/spamassassin/ to reflect tihs;

##{ 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. 2020+
##} FH_DATE_PAST_20XX

followed by zmcontrol stop ; zmcontrol start

[nrgyz]

How can I make sure this fix was applied successfully?

[jrefl5]

How about trying to send an e-mail to yourself then "Show Original" and see if the rule was hit, and/or the score assigned to it?

[nrgyz]

X-Spam-Score: -2.375... was originally -4.399

I conclude this was not applied. Is there a way to refresh SpamAssassin? I can't

zmconstrol stop; zmcontrol start

on my production environment right now!

[jrefl5]

How about zmantispamctl reload ??

[Vai0l0]

How about zmantispamctl reload ??

Worked Perfectly

Just edited
/opt/zimbra/conf/spamassassin/72_active.cf

from
...FH_DATE_PAST_20XX Date =~ /20[1-9][0-9]/ [if-unset: 2006]
to
...FH_DATE_PAST_20XX Date =~ /20[2-9][0-9]/ [if-unset: 2006]
and reloaded the antispam with

$ zmantispamctl reload
run as zimbra

[Sven Meeus]

Worked Perfectly

Just edited
/opt/zimbra/conf/spamassassin/72_active.cf

from
...FH_DATE_PAST_20XX Date =~ /20[1-9][0-9]/ [if-unset: 2006]
to
...FH_DATE_PAST_20XX Date =~ /20[2-9][0-9]/ [if-unset: 2006]
and reloaded the antispam with

$ zmantispamctl reload
run as zimbra

I see a lot of posts suggesting this change, but actually, what about the 9 years in between?

I did the change like this on our servers:

FH_DATE_PAST_20XX Date =~ /201[1-9]/ [if-unset: 2006]

This way, 2011 and above is considered as to futuristic, and not as of 2020 and above.
I tested it with my dekstop and a lab desktop with a future date above 2011 and it worked fine. I didn't do any of the other changes.

[phoenix]

I tested it with my dekstop and a lab desktop with a future date above 2011 and it worked fine. I didn't do any of the other changes.

Thanks for the update but you should post that on the spamassassin forums (or their bugzilla) as it's their problem.

[Mike Scholes]

I run Spamassassin on the same machine but independently from Zimbra and sa-update fixed the problem. Think it just downloads the latest rules and they include the 2010 bug fix.

[siomon.liu]

modify this file /conf/spamassassin/local.cf
add "score FH_DATE_PAST_20XX 0.0"

and zmamavisdctl restart