spamassassin-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzilla-dae...@issues.apache.org
Subject [Bug 6545] Include DNSWL spam reporting plugin
Date Sun, 20 Mar 2011 02:31:39 GMT
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6545

--- Comment #11 from Karsten Br├Ąckelmann <guenther@rudersport.de> 2011-03-19 22:31:33
EDT ---
(In reply to comment #10)
> There were requests for ability to report abuse to DNSWL here:

Thanks, Darxus. However... That was not a request for the ability to report.
That was a complaint about DNSWL hits downscoring spam, "just below the
threshold".

Particularly noteworthy about this is, that the threshold the user was talking
about is NOT the SA default threshold of 5.0, which is what's being used for
score generation -- but a threshold of 6.31, which is I believe a higher Amavis
default.

None of his sample headers provided scored below 6.0, still classified spam by
stock SA. He did not provide evidence (other than to you and Matthias
privately), and even mentioned inappropriate trusted and internal settings for
forwarders could have been causing this. There is no final conclusion on the
list. [1]

(And please ignore the sub-thread by Michelle, which, yet again, has been shown
to be due to incorrect trusted networks settings.)


So far, my assessment of Target Milestone 3.4 still stands. I have not seen
sufficient demand or potential users, to raise this for inclusion in the
current stable 3.3 branch -- which requires even more review and votes.


[1] Care to share what these samples have shown? Feel free to send the data to
    me privately, or the private@ list.

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