spamassassin-dev December 2011 archive
Main Archive Page > Month Archives  > spamassassin-dev archives
spamassassin-dev: [Bug 6718] DNSWL whitelist corruption

[Bug 6718] DNSWL whitelist corruption

From: <bugzilla-daemon_at_nospam>
Date: Sat Dec 10 2011 - 01:27:26 GMT
To: dev@spamassassin.apache.org

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6718

Kevin A. McGrail <kmcgrail@pccc.com> changed:

           What |Removed |Added
----------------------------------------------------------------------------
                 CC| |kmcgrail@pccc.com

--- Comment #2 from Kevin A. McGrail <kmcgrail@pccc.com> 2011-12-10 01:27:26 UTC ---
(In reply to comment #1)
> Additionally, their form for addition to the whitelist contains a 'very
> sophisticated' (<- sarcasm intended) bot check by asking for 5+3.
>
> Seriously. Removal of the DNSWL lists needs to be effected immediately, and
> whoever thought of authorising them in the first place prevented from any such
> action in the future.

Please attach a sample of a FP or FN from the rule. The scores for DNSWL are
graduated and I'm not aware of the systemic issue you are stating exist

# DNSWL
score RCVD_IN_DNSWL_NONE 0 -0.0001 0 -0.0001
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

In my hand-classified FNs folder, I have 292 hits for DNSWL that are:

246 - DNSWL_NONE
38 - DNSWL_LOW
4 - DNSWL_MED
4 - DNSWL_HI

Of the 4 hi, two were real bank notifications incorrectly classified and 2 were
from apache mailing lists.

Without samples, this has to be considered invalid. And I'm open to
consideration there is a problem but try and lower the rant and unnecessary
digs.

-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.