https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8376
Bug ID: 8376
Summary: RCVD_IN_VALIDITY_*_BLOCKED have high scores, producing
false positives
Product: Spamassassin
Version: 4.0.1
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Rules
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: Undefined
Ohai,
it seems at some point in February (probably via r1931878), the Validity
BLOCKED rules started to have "high" (non-0.001) scores, which result in mail
being falsely flagged as spam in some cases. Not sure whether this is related
to the change in r1931710 where they were removed from the force-active list.
The current scores are:
rulesrc/scores/72_scores.cf:score RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001
0.408 0.001 0.408
rulesrc/scores/72_scores.cf:score RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001
0.819 0.001 0.819
rulesrc/scores/72_scores.cf:score RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001
0.903 0.001 0.903
While other _BLOCKED rules have 0.001 0.001 0.001 0.001
What I don't really understand is, the main Validity rules have 0 score in
rules/50_scores.cf, as they are disabled by default -- why does the check still
happen at all? Or would one need to explicitly score BLOCKED to 0 too for that
to be disabled?
--
You are receiving this mail because:
You are the assignee for the bug.
