I haven’t got to the bottom of this yet, but thought I’d post about it in case anyone else is affected. A client running Hestia was complaining about not receiving mail. When I replied asking for more information, my own mail was rejected from his server saying my IP was banned at zen.spamhaus.org. However when I went to check at https://check.spamhaus.org/ its not listed. IP and all associated domain names are clear.
I can’t figure out what’s going on. In the meantime, I’ve edited /etc/exim/dnsbl.conf to remove spamhaus and restarted exim, so that is the quick fix.
OK, it hasn’t gone mad, but it seems to have been implementing the changes it threatened in 2021.
Basically if I query the zen.spamhaus.org server manually, I don’t get one of the expected codes any more, but a new one, which makes exim think that the IP address has been rejected, even though its not on the list. For example, if the server sending the mail’s IP is 188.8.131.52, I run the command.
dig -t txt +short 184.108.40.206.zen.spamhaus.org
"Error: open resolver; https://www.spamhaus.org/returnc/pub/220.127.116.11"
OK, thanks for those tests, kpv. I’ve been trying it out on a few servers, and have had very inconsistent results. Sometimes a server will report that the IP is blocked, and then when you send again a minute later, it passes through OK. After your post above, I think now what is happening is that those servers are using 18.104.22.168 and 22.214.171.124 randomly, so sometimes they fail and sometimes they don’t. A lightbulb moment.
resolvectl gives a lot of info on this.
I’ve forgotten why I changed the DNS to 126.96.36.199 and 188.8.131.52 originally. I think it was because the cloud host’s DNS servers were overloaded and not working. Anyway I’ll review this now with your results in mind.
Agree that exim should be able to distinguish the codes. However it doesn’t, and there is no code given on the spamhaus wiki for exim, just postfix, exchange etc. Maybe I’ll reach out for them.
For the record I did search the forum for spamhaus before posting, but didn’t turn up your post above. Thanks for pointing that out.
Just as a further note, I haven’t noticed any huge surge of spam since disabling the spamhaus check, so there doesn’t seem to be a huge downside in disabling it. I’ve also found a lot of other DNS are available, so might try one or two of those. eg. https://oper.io/src/nullspoon/dnsbl-check.git/tree/dnsbls.txt
I had the same issue couldn’t understand what was going on as it was intermitant and our IP was not on any blacklist even though the bounce back said it was. BTW We use Cloudflare Public DNS. This Thread has saved my mail!! Thanks @eris I did as you suggested and disabled spamhaus, mail flowing like a charm.
Exactly, aws was getting rejected, then tried gmail and it was getting rejected aswell.
What public dns you guys suggest that is good and works, apart from cloudflare and google that people say it is the culprit.
Or should I just keep spamhause removed ?