Date: Sat, 2 Jan 2010 12:00:12 GMT From: Michael Scheidell <scheidell@secnap.net> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/142216: mail/p5-Mail-SpamAssassin: fix FH_DATE_PAST_20XX for 2010 Message-ID: <201001021200.o02C0CrV024456@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/142216; it has been noted by GNATS. From: Michael Scheidell <scheidell@secnap.net> To: bug-followup@FreeBSD.org, thierry@pompo.net Cc: Subject: Re: ports/142216: mail/p5-Mail-SpamAssassin: fix FH_DATE_PAST_20XX for 2010 Date: Sat, 02 Jan 2010 06:55:20 -0500 This is a multi-part message in MIME format. --------------070701070904020306060909 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thank you for your bug submission. Keeping up any open source package depends on assistance from people who help, and port maintainers realy appreciate patch submissions like this one, full, complete, good explanation. However, in this case, the SpamAssassin approved solution is to use sa-update to update the rules, rather than patch the distribution rules. (sa-update should be run on all SA installations, nightly, in fact, sa 3.3.0 won't come with a standard ruleset and you will need to run sa-update ) In the case of Freebsd, there would be a lot of extra work on thousands of systems that maintain nightly builds, QA issues (even with a minor patch like this) due to the needed ports builds every time a port version is bumped. Please mark PR closed. Attached is the text from the SpamAssassin list notifying about the patch and the sa-update fix: -------- Original Message -------- Subject: Apache SpamAssassin Y2K10 Rule Bug - Update Your Rules Now! Date: Sat, 02 Jan 2010 02:38:13 -0500 From: Daryl C. W. O'Shea <spamassassin@dostech.ca> Organization: DOS Technologies To: Daryl C. W. O'Shea <spamassassin@dostech.ca> 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! 2010-01-01: 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 problem: 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. [4] On behalf of the Apache SpamAssassin project I apologize for this error and the grief it may have caused you. lters, SC Magazine 2008 _________________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com _________________________________________________________________________ --------------070701070904020306060909 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Thank you for your bug submission. Keeping up any open source package depends on assistance from people who help, and port maintainers realy appreciate patch submissions like this one, full, complete, good explanation.<br> <br> However, in this case, the SpamAssassin approved solution is to use sa-update to update the rules, rather than patch the distribution rules.<br> (sa-update should be run on all SA installations, nightly, in fact, sa 3.3.0 won't come with a standard ruleset and you will need to run sa-update )<br> <br> In the case of Freebsd, there would be a lot of extra work on thousands of systems that maintain nightly builds, QA issues (even with a minor patch like this) due to the needed ports builds every time a port version is bumped. Please mark PR closed.<br> <br> Attached is the text from the SpamAssassin list notifying about the patch and the sa-update fix:<br> <br> <br> <br> -------- Original Message -------- <table class="moz-email-headers-table" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject: </th> <td>Apache SpamAssassin Y2K10 Rule Bug - Update Your Rules Now!</td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th> <td>Sat, 02 Jan 2010 02:38:13 -0500</td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th> <td>Daryl C. W. O'Shea <a class="moz-txt-link-rfc2396E" href="mailto:spamassassin@dostech.ca"><spamassassin@dostech.ca></a></td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Organization: </th> <td>DOS Technologies</td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th> <td>Daryl C. W. O'Shea <a class="moz-txt-link-rfc2396E" href="mailto:spamassassin@dostech.ca"><spamassassin@dostech.ca></a></td> </tr> </tbody> </table> <br> <br> <pre>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! 2010-01-01: 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 problem: 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. [4] On behalf of the Apache SpamAssassin project I apologize for this error and the grief it may have caused you.</pre> lters, SC Magazine 2008 <div class="moz-signature"></div> <br> <div id="disclaimer.secnap.com"><hr> <p>This email has been scanned and certified safe by SpammerTrap®. <br />For Information please see <a href="http://www.spammertrap.com">www.spammertrap.com</a></p>; <hr></div> <br> </body> </html> --------------070701070904020306060909--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201001021200.o02C0CrV024456>