On 2022-03-11 at 22:34:14 UTC-0500 (Fri, 11 Mar 2022 21:34:14 -0600) Matt Saladna <m...@apisnetworks.com> is rumored to have said:
Spamhaus began flagging Cloudflare's servers, 1.0.0.1/1.1.1.1 as public resolver resulting in the error message. Other DNSBLs pick up responsibility, so the judgment shouldn't rely squarely on a bad response like 127.255.255.255, "excessive number of queries". One would hope a 900 second TTL offloaded to one of the largest resolvers would reduce their DNS load.
Which in no way justifies people who misunderstand documentation shooting themselves in the foot by rejecting all mail as self-flagellation. One absolutely should not score DNSBL responses that are completely unrelated to the specific value being queried for.
For a multiplexed DNSBL like Zen, it makes no sense to configure on a default+exceptions model. The information a Zen listing provides is entirely different depending on the value of the response and Spamhaus could add new responses at any time if they want to convey some other discrete fact about listed IPs.
-- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire
