[BlueOnyx:03219] Re: attn: all SpamAssassin users

[Larry Smith]

On Fri January 1 2010 16:30, Michael Stauber wrote:
> Hi all,
>
> > See if incomming messages hit the "FH_DATE_PAST_20XX" rule. If that's the
> > case, you should perform the following three steps:
>
> Actually it's a bit more complicated to fix this problem.
>
> SpamAsssassin typically is (or should be!) configured to use "sa-update" to
> to fetch the latest rules periodically. When the SpamAssassin team was made
> aware of the problems with the rule "FH_DATE_PAST_20XX", they pushed an
> update, but it's apparently the wrong one and not yet present on all
> mirrors.
>
> So here's the fix again, more detailed this time:
>
> 1.)  Edit /usr/share/spamassassin/50_scores.cf and find this line:
>
> score FH_DATE_PAST_20XX 2.075 3.384 3.554 3.188 # n=2
>
> Change it to this:
>
> score FH_DATE_PAST_20XX 0 0 0 0  # n=2
>
> 2.) If your SpamAssassin uses (or used!) sa-update, check if you have this
> file:
>
> /var/lib/spamassassin/3.002005/updates_spamassassin_org/50_scores.cf
>
> In it also find this line:
>
> score FH_DATE_PAST_20XX 2.075 3.384 3.554 3.188 # n=2
>
> Change it to this:
>
> score FH_DATE_PAST_20XX 0 0 0 0  # n=2
>
> However, depending on when your "sa-update" runs the problem could come
> back if the SpamAssassin makers haven't managed to push out the fixed rules
> by then.
>
> 3.) Restart Spamassassin.

An alternative, without disabling the rule, is to find the line in 
72_active.cf:

>header   FH_DATE_PAST_20XX      Date =~ /20[1-9][0-9]/ [if-unset: 2006]^M

and change it to read:

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

(Note the 2-9 change vice 1-9).  This changes spamassassin to "fire"
on dates past 2020 until a patch is released widescale.

-- 
Larry Smith
lesmith at ecsis.net