https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6668
--- Comment #10 from Kevin A. McGrail <[email protected]> 2011-10-03 19:34:17 UTC --- > That sounds great to me as well. Although I'd prefer something in the wiki > for > maintainability, I don't know, maybe > http://wiki.apache.org/spamassassin/XBLAbuse ? Again, generic and I don't consider this necessarily "abuse". That's a very strong word to many people. To me, it's an error requiring administrative attention with a landing page to help them try and resolve the issue. Nothing more, nothing less. > You mis-read what I said. I never suggested false positives (in fact I > suggested it was bad that SEM intentionally caused false positives). I was > talking about causing false negatives (spam being marked as non-spam). That is not the correct definition of a FN in my opinion. By your definition, any email that got through SA for any reason is a False Negative. We have to ship SA in a way that is safe for the vast majority of users which might not be the most effective for blocking all Spam. > So the question is, what are acceptable methods of enforcing those > thresholds? > Blocking queries resulting in delay of email is acceptable to you. I don't > know how effective that is in getting people to stop querying, and it doesn't > provide any feedback to indicate that there is a problem. Is it acceptable to > cause false-negatives, spam being marked as non-spam, with clear indication > (via a matching rule and description) of what the problem is? PRIMARILY, I want to see a method which doesn't artificially change the SA scoring up or down substantially. An RBL that starts returning ALL true or ALL false for over-limit issues is artificially changing the scores. No answer or a answer handled as an error would be acceptable. At worst, the queries can be stopped by blackholing the requests from overlimit IPs. So this is really a matter for the RBL to handle. However, some RBLs want to convert those over-limit users into customers and they do so through harmful techniques to get the admin's attention. Regards, AKM -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
