Bug 927 - MAY_BE_FORGED low-performing rule pruned
Summary: MAY_BE_FORGED low-performing rule pruned
Status: RESOLVED WONTFIX
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P4 trivial
Target Milestone: ---
Assignee: Justin Mason
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-17 09:38 UTC by Justin Mason
Modified: 2002-12-19 23:50 UTC (History)
0 users



Attachment Type Modified Status Actions Submitter/CLA Status

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Mason 2002-09-17 09:38:09 UTC
Removed MAY_BE_FORGED from HEAD cvs.

hit frequencies:

OVERALL%   SPAM% NONSPAM%     S/O    RANK   SCORE  NAME
  2.530    3.757    2.290    0.62    0.34    0.00  MAY_BE_FORGED

test code from all files in rules dir:

header MAY_BE_FORGED            Received =~ /\(may be forged\)/i
describe MAY_BE_FORGED          'Received:' has 'may be forged' warning


If you want to re-add this test to SpamAssassin, please follow
up this bug entry, improving the code until the S/O ratio
goes above 0.7 (or below 0.3 for nice tests).

(automated submission)
Comment 1 Daniel Quinlan 2002-09-20 05:28:18 UTC
Whatever adds that header, it seems to work, more or less.

It matches  2.77% of my spam and 0.32% of my nonspam.

That's an S/O of .90.  Not too bad.  I just have a gut-feeling that this rule
might be worth keeping for the sake of letting the GA do its thing.
Comment 2 Justin Mason 2002-09-20 09:43:55 UTC
I think it's one of those things that some ISPs/mail hosts add
all of the time, and some others do not; so it's stats will wildly
vary depending on whose corpus it's running on. just my hunch.
Comment 3 Justin Mason 2002-12-20 08:48:50 UTC
old, broken rules that nobody wanted; closing
Comment 4 Justin Mason 2002-12-20 08:50:38 UTC
closed, I said!
Comment 5 Justin Mason 2002-12-20 08:50:45 UTC
closed, I said!