https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6525
Ben Dugdale <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #32 from Ben Dugdale <[email protected]> 2011-08-11 17:55:12 UTC --- I'll give a +1 for removing NJABL but for another reason. We had a user get an infection on their PC and get our mail server (64.18.62.36) on the dnsbl.njabl.org list. Rightly so. The problem is that the list administration is unresponsive to requests to be removed now that we have corrected the problem. I take it that nobody is monitoring the removal address. This behavior is going to lead to false positives in the long run. PS. I'm sure you will all assume that we run a lousy mail system (it seems most do) and it's true that something slipped past us but FYI we block direct-mail, only accept mail submissions for authenticated users, do not relay for anyone, publish a SPF record, etc. We really strive to provide a responsible and RFC-compliant mail system. I guess the next step for us is outbound spam filtering and more careful outbound rate limiting. Even then, the whole system is reactionary and does not help for the first $n entities to get hit with an infection. Someone needs to responsibly handle RBL removal requests or the system is broken. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
