https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6269
--- Comment #19 from Jonathan <[email protected]> 2010-01-01 14:42:31 UTC --- (In reply to comment #18) > On my system the path is: > /var/lib/spamassassin/3.002005/updates_spamassassin_org/72_active.cf Oops, my bad. > After seeing it was wrong, I manually edited the file to fix it. That is not what I asked for. Next time please take care in following instructions as we need to diagnose when things go wrong in order to see if it is a bug or a failure on your side. What you just did was covering your tracks and destroying trails. > But as I said, it still had the old pattern. But the filedate was new, i.e. > > it was updated. Do you still have the log of the update? Does it show something like this: [11358] dbg: channel: metadata version = 795855 [11358] dbg: dns: 5.2.3.updates.spamassassin.org => 895075, parsed as 895075 > Now it is: > ##{ 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 > > (I changed the 1-9 into 2-9) This will not stick normally and should be reset to whatever the update channels holds on the next run of sa_udpate. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
