On 2022-05-13 12:57, Grant Taylor via mailop wrote:

I suspect that their $BLOCKING method has progressed to false positives as a way to get email administrator's attention.

It's progressed to false positives because some people run mail servers who aren't parsing DNSBL return codes right. The best way to operate is to enumerate what return codes the DNSBLs your mail server uses, and ignore ALL OTHER DNSBL return codes. Especially those that start with 127.255, or anything else outside of 127/8. When you see weird return codes, your mail server should ignore them EXCEPT for telling you somehow that that DNSBL is behaving strangely and should be looked at.

It'll also protect you from a situation where a DNSBL gets grabbed by a domain squatter, and their DNS serversreturn some random IP address for every query that's pointing at their marketing site.

My recollection is that the planned cut off date was 6 or more weeks ago.  So I feel like they gave ample grace time after the published cut off date.

This situation vis-a-vis Spamhaus has been in place for well over a year. Nothing has changed, except they may have identified a new open resolver being used to abuse the free query limits.

Get a DQS key (free for low volume users), and these problems go away.
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop

Reply via email to