On Fri, 11 Feb 2011, Lawrence @ Rogers wrote:
Hello,
Like many users, we set our required score to 5.0. Lately, we've seen
several dozen ham e-mails get mislabeled as spam due to one rule that
(usually) has a score of 3 or more. For example, please see the attached
e-mail (raw with headers) where TO_NO_BRKTS_DIRECT contributes over 3 to
the overall score.
We've already had to create a custom .cf file to rescore rules like
EXCUSE_REMOVE for this purpose.
What I propose is a limit of 2.5 for any rule that is not a network test
(RBL, DNSBL) or a Bayesian rule (BAYES_xx). This would allow the rules
to still effectively tag spam as they should, while reducing the
possibility of false positives.
Thoughts?
Unfortunately I can't comment on the idea of modifying the scoring system
to impose an upper limit on individual rule scores, as I'm not that
familiar with its internal details. I personally don't see any problem
with the idea, but it's possible it could keep actual spam that only hits
a few rules from being scored in a way that it would reach 5 points.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
[email protected] FALaholic #11174 pgpk -a [email protected]
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
A well educated Electorate, being necessary to the liberty of a
free State, the Right of the People to Keep and Read Books,
shall not be infringed.
-----------------------------------------------------------------------
Today: Abraham Lincoln's and Charles Darwin's 202nd Birthdays
