SA Bugzilla – Bug 5641
Spamhaus is non-free for commercial use
Last modified: 2015-04-12 15:30:38 UTC
Matt Kettler wrote: > Should we disable Spamhaus by > default as we've done in the past for razor and DCC? They're no longer > "free for everyone", and actually even reasonably small networks can't > use them for free (100 user limit). Theo Van Dinter wrote: > Sounds reasonable to me. Daryl C. W. O'Shea wrote: > This has been on my mind for a while. I'd hate to lose accurate scoring > on a set of rules that hits such a large proportion of mail. Justin Mason wrote: > good point about Spamhaus... 100 user limit is tiny! We may > indeed have to do something about that, but I agree with Daryl; the > Spamhaus rules are very accurate.
In my experience almost all of Spamhaus hits come from their inclusion of cbl.abuseat.org in xbl, and it would be a good substitute since their terms of service are not restrictive (see http://cbl.abuseat.org/tandc.html).
With regards to CBL, they specifically state that they would prefer users to not querry CBL directly, but use XBL instead. It's not in their T&C, however, we should at least open a dialog with CBL before making that change. See the "DNSBL Setup Recommendations" section of: http://cbl.abuseat.org/faq.html Where it states: "Generally speaking, we prefer users to use the SpamHaus DNSBL system to get access to the CBL, instead of the CBL directly. " And also: "WARNING: it is CBL policy that spam filter and spam filter service vendors MUST obtain a paid-for feed from Spamhaus. Filter providers that do not have a paid-for feed from Spamhaus, or who have not registered for the CBL feed, MAY find themselves inhibited from obtaining a CBL feed without warning."
moving most remaining 3.3.0 bugs to 3.3.1 milestone
reassigning, too
moving all open 3.3.1 bugs to 3.3.2
Moving back off of Security, which got changed by accident during the mass Target Milestone move.
Moving all open bugs where target is defined and 3.4.0 or lower to 3.4.1 target
Free for all is not a requirement of the DNSBL policy written after this ticket was open. See https://wiki.apache.org/spamassassin/DnsBlocklistsInclusionPolicy