Homepage   Open Systems 
 Personal   What is FLOSS? 
 Clients, Associates   Services 
 PDF and other Viewers   Network Status 
Subscribe to receive messages automatically in email.

NOTICE: Apache SpamAssassin Y2K10 Rule Bug - Update Your Rules Now (fwd)

From: Russell McOrmond <russell@flora.ca>
Date: Sun, 3 Jan 2010 10:42:13 -0500 (EST)

   I set "score FH_DATE_PAST_20XX 0" in the config file.  Hugli (Mail and 
DNS server) is the one virtual server I didn't have a chance to sidegrade 
to CentOS yet.

  Russell McOrmond, Internet Consultant: <http://www.flora.ca/>
  Please help us tell the Canadian Parliament to protect our property
  rights as owners of Information Technology. Sign the petition!
  http://digital-copyright.ca/petition/ict/     http://KillBillC61.ca

  "The government, lobbied by legacy copyright holders and hardware
   manufacturers, can pry control over my camcorder, computer,
   home theatre, or portable media player from my cold dead hands!"

---------- Forwarded message ----------
Date: Sat, 2 Jan 2010 08:57:58 -0800 (PST)
From: Sally Khudairi
To: announce@apache.org
Subject: NOTICE: Apache SpamAssassin Y2K10 Rule Bug - Update Your Rules Now

The following notice has been sent by Daryl C.W. O'Shea, VP of Apache 
SpamAssassin --

I've posted the following note on the Apache SpamAssassin website [1] 
about an issue with a rule that may cause wanted email to be classified as 
spam by SpamAssassin.  If you're running SpamAssassin 3.2.x you are 
encouraged to update you rules (updates were released on sa-update around 
1900 UTC Jan 1, 2010).

Y2K10 Rule Bug - Update Your Rules Now!


Versions of the FH_DATE_PAST_20XX [2] rule released with versions of 
Apache SpamAssassin 3.2.0 thru 3.2.5 will trigger on most mail with a Date 
header that includes the year 2010 or later.  The rule will add a score of 
up to 3.6 towards the spam classification of all email.  You should take 
corrective action immediately; there are two easy ways to correct the 

1) If your system is configured to use sa-update [3] run sa-update now. An 
update is available that will correct the rule.  No further action is 
necessary (other than restarting spamd or any service that uses 
SpamAssassin directly).

2) Add "score FH_DATE_PAST_20XX 0" without the quotes to the end of your 
local.cf file to disable the rule.  If you require help updating your 
rules to correct this issue you are encouraged to ask for assistance on 
the Apache SpamAssassin Users' list.  Users' mailing list info is here. 

On behalf of the Apache SpamAssassin project I apologize for this error 
and the grief it may have caused you.

[1] http://spamassassin.apache.org/
[2] http://wiki.apache.org/spamassassin/Rules/FH_DATE_PAST_20XX
[3] http://wiki.apache.org/spamassassin/RuleUpdates
[4] http://wiki.apache.org/spamassassin/MailingLists
Status mailing list

Read: [next] [previous] message
List: [newer] [older] articles