https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6251
Summary: Temporarily Reduce DNSWL scores for 3.3.0 release
Product: Spamassassin
Version: 3.3.0
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: Rules
AssignedTo: [email protected]
ReportedBy: [email protected]
Similar to Bug #6247 for Return Path, I believe we should reduce the scores of
DNSWL before the 3.3.0 release.
http://ruleqa.spamassassin.org/20091205-r887515-n
Weekly masscheck for many weeks have been showing a minor but consistent amount
of false positives in DNSWL medium and low. As a matter of practice I
generally do not report whitelist violations or blacklist FP's because doing so
would artificially bias the ruleqa statistics without solving underlying
problems in listing and removal policy.
Current 50_scores.cf:
score RCVD_IN_DNSWL_LOW 0 -1 0 -1
score RCVD_IN_DNSWL_MED 0 -4 0 -4
score RCVD_IN_DNSWL_HI 0 -8 0 -8
My concerns:
* DNSWL has no obvious and easy methods on their site to report violations
where spam was sent from a DNSWL listed host.
* Does DNSWL currently use spam traps as an automated method to detect
whitelist violations? I don't know. Whatever their regular practices are, I
strongly believe that automation is the only sustainable way for a service of
nature to be maintainable in the long-term.
* GA rescoring when DNSWL was allowed to float assigned much lower scores than
our fixed scores.
score RCVD_IN_DNSWL_LOW 0 -0.7 0 -0.7
score RCVD_IN_DNSWL_MED 0 -2.3 0 -2.3
score RCVD_IN_DNSWL_HI 0 -5 0 -5
I believe we should ship 3.3.0 with these as a reasonable score. After 3.3.0
release, if DNSWL clarifies the above concerns and the DNSWL statistics in
ruleqa improve due to methodology (not one-off corpus cleaning) then I believe
it would be fully appropriate to increase the scores in sa-update.
Comments?
Votes?
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
