SA Bugzilla – Bug 927
MAY_BE_FORGED low-performing rule pruned
Last modified: 2002-12-19 23:50:45 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)
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.
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.
old, broken rules that nobody wanted; closing
closed, I said!