Read through the bug report, from what I understand we should just run the following??
/etc/cron.d/sa_update
Yes, but it will be done overnight as well. You can check the logs send to the admin and see if the version gets updated to minimum version 895063.
To check the rule really is there you can do this:
grep -R '20\[2-9\]\[0-9\]' /var/lib/spamassassin/3.002005/updates_spamassassin_org/72_active.cfIt should output this:
header FH_DATE_PAST_20XX Date =~ /20[2-9][0-9]/ [if-unset: 2006]The first digit group after 20 should say [2-9] and not [1-9].
or must we do the following?..??
mkdir -p /etc/e-smith/templates-custom/etc/mail/spamassassin/local.cf
echo score FH_DATE_PAST_20XX 0.0 >> /etc/e-smith/templates-custom/etc/mail/spamassassin/local.cf/99FH_DATE_PAST_20XX
signal-event email-update
No, as that was the work around until the bug got fixed as you could have read in the bug report.
I am going to run a yum update to make sure all the servers have the latest packages, but not sure what else to do..
Although that is a good thing it will not update the faulty rule as this will not be fixed until spamassassin 3.2.6 is released. The updated rule is pushed to the update channel from which sa_update takes it's definitions and should therefore update it through that path.
Since it was pushed at Jan 1st, 2010 12:54 UTC. Any update using sa_update afterwards should have picked this up. sa_update runs around 4.00 local time at night on your machine, so most likely you received the update on Jan 2nd.
8 Replies
3288 Views