SA Bugzilla – Bug 74
bad rules lead to bad GA scores
Last modified: 2002-06-15 03:58:08 UTC
Poorly specified rules like S[letter e]CTION_301 (which is basically /s[e]ction.*301/i) which have great potential for matching spam have actually ended up with NEGATIVE scores from the GA scoring because they are not specific enough. If that rule were better written to match actual instances of S.301 legislation it would surely get a positive GA score and be a useful rule. I'm sure there are other instances.
Subject: Re: New: bad rules lead to bad GA scores Patches happily accepted. Worth noting that after modifying the GA, the new score generated for that rule is now a more meaningful 1.650 bugzilla-daemon@hughes-family.org wrote: > Date: Sat, 2 Mar 2002 22:57:08 -0800 (PST) > From: bugzilla-daemon@hughes-family.org > To: craig@hughes-family.org > Subject: [Bug 74] New: bad rules lead to bad GA scores > > http://www.hughes-family.org/bugzilla/show_bug.cgi?id=74 > > Summary: bad rules lead to bad GA scores > Product: Spamassassin > Version: 2.1CVS > Platform: All > OS/Version: FreeBSD > Status: NEW > Severity: normal > Priority: P2 > Component: Rules > AssignedTo: craig@hughes-family.org > ReportedBy: ben@ben.com > > > Poorly specified rules like S[letter e]CTION_301 (which is basically > /s[e]ction.*301/i) which have great potential for matching spam have actually > ended up with NEGATIVE scores from the GA scoring because they are not specific > enough. If that rule were better written to match actual instances of S.301 > legislation it would surely get a positive GA score and be a useful rule. > > I'm sure there are other instances. > > > > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > > >
Really a little vague to accept as a bug. If you have specific suggestions for specific rules, please reopen or file new bugs.