https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6048
--- Comment #12 from Matt Kettler <[email protected]> 2009-01-22 03:53:51 PST --- > SA should consider one or more of the following actions: > > a) reconsider making URIBL_* rules default on, by making them default off, > allowing capable users the choice to use them and their potential future > fallout. > > b) add code to somehow detect the "no-service" situation and subsequently > discontinue querying uribl.com > > c) give a much lower score to URIBL_* rules. > I've already proposed: d) add rules that detect the "no-service" situation and subsequently increase attention so the admins can take their own action to stop querying it. And I think that's a valid option. b) would work too, but that's a bit tricky since SpamAssassin would loose this information every time a new instance was created, and have to relearn it. That might throttle the problem a bit, reducing the query load to only happen once each time a new spamd child is created, but it wouldn't solve it for Alex. a) has already been discussed at length, and as far as I'm concerned, it is off the table. We've discussed the whole "free for most but not high load" topic at length regarding both Uribl and SpamHaus. No service, free or paid, can withstand infinite load, so all services need a cutoff somewhere, written or otherwise. One mans daily traffic is another mans DoS attack. c) defeats the purpose of using URIBL in SA in the first place. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
