On 2011-02-11 19:38, 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?
my thought would be to fix the html only mail, header formating, etc in
your sample, before working around filter rules
