https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6048
--- Comment #11 from Matt Kettler <[email protected]> 2009-01-22 03:45:39 PST --- Alex, I take a bit of exception to this statement: "Matt's solution suggestion breaks the URIBL.com's intention of warning the admin that he's abusing the mirrors, even AFTER being contacted and the query hammering would continue." My solution doesn't break that intention, it makes it clearer that they are being blocked by URIBL. I'm not suggesting that this over-ride the scores of URIBL_BLACK, or otherwise disable that rule. I'm suggesting it be added so admins quickly know why URIBL_BLACK starts matching all messages. In fact, URIBL_SERVERBLOCKED probably should have a quite significant score on its own. (ie: +20) So a hypothetical system which is blocked would start seeing both URIBL_BLACK and URIBL_SERVERBLOCKED match. At that point it should, theoretically, be very clear to them why it's going on. In the current situation, they'll see URIBL_BLACK match all messages, but there's nothing telling them why. Let's work together on a solution that does make it abundantly clear. This will be better for URIBL, as you'll get quicker reactions from the folks your blocking (if they're using SpamAssassin). Of course, we'll have to deal with "Why doesn't it just offset the score of URIBL_BLACK so my mail keeps working" type questions, but wouldn't work as the intent of the rule is to raise awareness, not dull the pain. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
