https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6270
Summary: SpamAssassin wrongfully tagging mail with
FH_DATE_PAST_20XX since Jan 1st, 2010
Product: Spamassassin
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: critical
Priority: P5
Component: sa-update
AssignedTo: [email protected]
ReportedBy: [email protected]
Created an attachment (id=4617)
--> (https://issues.apache.org/SpamAssassin/attachment.cgi?id=4617)
Wrongfully FH_DATE_PAST_20XX tagged e-mail
Since I am not sure where to report this, I am filing against sa_learn. If this
is not the proper component please tell me and if known tell me where to go to
get this fixed as due to the high score users run the risk of e-mail being
dropped where it should not have happened.
We use spamassassin packaged by ATrpms on SME Server (http://www.contribs.org)
as well as sa_learn to update the rules.
Now it seems that since Jan 1st, 2010 all incoming mail is scored for
FH_DATE_PAST_20XX, without exception.
This bug was fixed half a year ago in SpamAsassin
(https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5852), but it seems the
sa_learn script still pulls the faulty rule in:
[r...@homer spamassassin]# pwd
/var/lib/spamassassin
[r...@homer spamassassin]# grep -R FH_DATE_PAST_20XX *
3.002001/updates_spamassassin_org/50_scores.cf:score FH_DATE_PAST_20XX 2.075
3.384 3.554 3.188 # n=2
3.002001/updates_spamassassin_org/72_active.cf:##{ FH_DATE_PAST_20XX
3.002001/updates_spamassassin_org/72_active.cf:header FH_DATE_PAST_20XX
Date =~ /20[1-9][0-9]/ [if-unset: 2006]
3.002001/updates_spamassassin_org/72_active.cf:describe FH_DATE_PAST_20XX
The date is grossly in the future.
3.002001/updates_spamassassin_org/72_active.cf:##} FH_DATE_PAST_20XX
3.002002/updates_spamassassin_org/50_scores.cf:score FH_DATE_PAST_20XX 2.075
3.384 3.554 3.188 # n=2
3.002002/updates_spamassassin_org/72_active.cf:##{ FH_DATE_PAST_20XX
3.002002/updates_spamassassin_org/72_active.cf:header FH_DATE_PAST_20XX
Date =~ /20[1-9][0-9]/ [if-unset: 2006]
3.002002/updates_spamassassin_org/72_active.cf:describe FH_DATE_PAST_20XX
The date is grossly in the future.
3.002002/updates_spamassassin_org/72_active.cf:##} FH_DATE_PAST_20XX
3.002003/updates_spamassassin_org/50_scores.cf:score FH_DATE_PAST_20XX 2.075
3.384 3.554 3.188 # n=2
3.002003/updates_spamassassin_org/72_active.cf:##{ FH_DATE_PAST_20XX
3.002003/updates_spamassassin_org/72_active.cf:header FH_DATE_PAST_20XX
Date =~ /20[1-9][0-9]/ [if-unset: 2006]
3.002003/updates_spamassassin_org/72_active.cf:describe FH_DATE_PAST_20XX
The date is grossly in the future.
3.002003/updates_spamassassin_org/72_active.cf:##} FH_DATE_PAST_20XX
3.002004/updates_spamassassin_org/50_scores.cf:score FH_DATE_PAST_20XX 2.075
3.384 3.554 3.188 # n=2
3.002004/updates_spamassassin_org/72_active.cf:##{ FH_DATE_PAST_20XX
3.002004/updates_spamassassin_org/72_active.cf:header FH_DATE_PAST_20XX
Date =~ /20[1-9][0-9]/ [if-unset: 2006]
3.002004/updates_spamassassin_org/72_active.cf:describe FH_DATE_PAST_20XX
The date is grossly in the future.
3.002004/updates_spamassassin_org/72_active.cf:##} FH_DATE_PAST_20XX
3.002005/updates_spamassassin_org/50_scores.cf:score FH_DATE_PAST_20XX 2.075
3.384 3.554 3.188 # n=2
3.002005/updates_spamassassin_org/72_active.cf:##{ FH_DATE_PAST_20XX
3.002005/updates_spamassassin_org/72_active.cf:header FH_DATE_PAST_20XX
Date =~ /20[1-9][0-9]/ [if-unset: 2006]
3.002005/updates_spamassassin_org/72_active.cf:describe FH_DATE_PAST_20XX
The date is grossly in the future.
3.002005/updates_spamassassin_org/72_active.cf:##} FH_DATE_PAST_20XX
[r...@homer spamassassin]#
We are taking rules from the following channels:
[r...@homer cron.daily]# cat /etc/mail/spamassassin/channels
updates.spamassassin.org
saupdates.openprotect.com
[r...@homer cron.daily]#
Since this file seems to come from updates.spamassassin.org I am reporting this
here.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
