From: "R-Elists" <list...@abbacomm.net>
Date: Fri, 1 Jan 2010 15:48:13 -0800
> Cc: Spamassassin users list
> Subject: Re: [sa] Re: FH_DATE_PAST_20XX
>
> Damn -- mea culpa. When we fixed the bug in SVN trunk in bug
> 5852, I should have immediately backported it to the 3.2.x
> sa-update channel when I commited that patch, but I didn't.
>
> It's now fixed in updates, but that won't help the admins
> who've been paged to deal with high FP rates on a holiday.
> :( Sorry folks...
>
> --j.
what should the new rule look like?
i mean, i get it, and i think i know, and i even tested it and it was still
failing even after a restarts...
soooo...
seriously, i disabled the rule early AM yet when the update came through 4
or so hours later, i believe it looks exactly the same as when i first
viewed it early on...
The easiest way to see what is being changed since your last sa-update
is to first sa-update /tmp and diff. The change is trivial but significant...
root% sa-update -D --updatedir /tmp/updates
root% diff -r -U 0 /var/lib/spamassassin/3.002005/updates_spamassassin_org
/tmp/updates/updates_spamassassin_org
diff -u -w --minimal -r -U 0
/var/lib/spamassassin/3.002005/updates_spamassassin_org/72_active.cf
/tmp/updates/updates_spamassassin_org/72_active.cf
--- /var/lib/spamassassin/3.002005/updates_spamassassin_org/72_active.cf
2009-07-20 17:01:55.000000000 -0400
+++ /tmp/updates/updates_spamassassin_org/72_active.cf 2010-01-01
18:51:10.000000000 -0500
@@ -527,7 +527,7 @@
##{ FH_DATE_PAST_20XX
-header FH_DATE_PAST_20XX Date =~ /20[1-9][0-9]/ [if-unset: 2006]
+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
-jeff
