Incorrect IPv4 Spamhaus error

What type of hardware are you using: VPS bought online
What YunoHost version are you running: 13.0.8 (testing)
How are you able to access your server: The webadmin

Describe your issue

I see the following in my diagnostics :

=================================
Email (mail)
=================================

[ERROR] Your IP or domain 57.129.175.185 is blocklisted on Spamhaus ZEN
 - It looks like the reason mentions 'open resolver'.This usually means your server is not using its local DNS, but a public, open, one. Check the contents of /etc/resolv.conf, it should contain nameserver 127.0.0.1.Since this file is usually automatically generated, do not edit it manually. Check your DHCP settings, or your VPN settings if you are using one, or if you used a Debian image made by, for example, a VPS provider, look for a cloudinit configuration. You are most welcome on the YunoHost support channels to get help on this issue. The verbatim blacklist reason is: "Error: open resolver; https://check.spamhaus.org/returnc/pub/2001:41d0:801:2000::8397/"
 - After identifying why you are listed and fixing it, feel free to ask for your IP or domain to be removed on https://www.spamhaus.org/zen/

[ERROR] Your IP or domain 2001:41d0:801:2000::8397 is blocklisted on Spamhaus ZEN
 - It looks like the reason mentions 'open resolver'.This usually means your server is not using its local DNS, but a public, open, one. Check the contents of /etc/resolv.conf, it should contain nameserver 127.0.0.1.Since this file is usually automatically generated, do not edit it manually. Check your DHCP settings, or your VPN settings if you are using one, or if you used a Debian image made by, for example, a VPS provider, look for a cloudinit configuration. You are most welcome on the YunoHost support channels to get help on this issue. The verbatim blacklist reason is: "Error: open resolver; https://check.spamhaus.org/returnc/pub/2001:41d0:801:2000::8397/"
 - After identifying why you are listed and fixing it, feel free to ask for your IP or domain to be removed on https://www.spamhaus.org/zen/

The second error is correct.

The first, however is incorrect. Its reporting an issue with my IPv4 address (where there isn’t one) and the link contains the IPv6 address.

BTW I’m curious where this info comes from … other checking sites, such as Error - MxToolBox, give different info.

Share relevant logs or error messages

See above

“Open resolver” means your server is using an open-to-all DNS resolver, and Spamhaus and other blocklist services do not like that. YunoHost servers use their internal DNS resolver by default, but it’s quite possible your VPS provider has applied some customization to your base Debian configuration.

First, check that your /etc/resolv.conf file contains nameserver 127.0.0.1. Then can you look for DNS configuration on your VPS’ IP settings, related to its network interfaces or something called cloudinit, maybe? The idea is the set them to use your DNS server hosted on 127.0.0.1, not something else.

Check also that your port 53 is NOT opened on UDP on your firewall.

Thanks for your reply.

Yes, my /etc/resolv.conf just has 127.0.0.1 so, presumably, is resolved through my hosting service (ovhcloud).

But I think you missed my question. The first error reported has

[ERROR] Your IP or domain 57.129.175.185 … Error: open resolver; https://check.spamhaus.org/returnc/pub/2001:41d0:801:2000::8397/

ie starts with an IPv4 address (which is valid as far as spamhaus is concerned) and has a link to a IPv6 URL. I wondered if this is a duff error message.

Thats why I was asking where these error comes from.

Digging further, I do see in mail.log.1 -

2026-11-09T13:54:26.201904+00:00 u3acommunities postfix/smtpd[84610]: NOQUEUE: reject: RCPT from unknown[72.138.7.190]: 554 5.7.1 Service unavailable; Client host [72.138.7.190] blocked using zen.spamhaus.org; Error: open resolver; https://check.spamhaus.org/returnc/pub/2001:41d0:801:2000::8397/; from=verify@example.org to=q4e8fb880d0bc1d@atendimento25x.sorofisiolook.reisen proto=ESMTP helo=<example.org>

which looks like yunohost rejecting (correctly?) an incoming email attempt.

Assuming this is where yunohost diagnostics is getting the error from, should it ignore this type of error message ? ie I don’t think its indicating a problem with be server, but a problem with the server sending email.

Many thanks again, I hope this makes sense :slight_smile:

Pete

Reading the source I see yunohosts gets this info from various DNS servers. I had no idea you could do that !

So in my case, I see -

$ dig 185.175.129.57.zen.spamhaus.org TXT

....

185.175.129.57.zen.spamhaus.org. 2100 IN TXT	"Error: open resolver; https://check.spamhaus.org/returnc/pub/2001:41d0:801:2000::8397/"

and

$ dig 7.9.3.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.1.0.8.0.0.d.1.4.1.0.0.2.zen.spamhaus.org TXT

...

7.9.3.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.1.0.8.0.0.d.1.4.1.0.0.2.zen.spamhaus.org. 2100 IN TXT "Error: open resolver; https://check.spamhaus.org/returnc/pub/2001:41d0:801:2000::8397/"

My /etc/resolv.conf references 127.0.0.1, so dnsmasq, which is configured by yunohost.

Tracing the network queries I see

2a00:12a8:8000::fff0:3 returns Error: open resolver
2a05:f480:2000:1246:9998:cf46:6cf8:1e7a returns Error: open resolver
vds-527288.hosted-by-itldc.com returns Error: open resolver
2001:648:2000:340:68b:900d:39:b036 returns Error: open resolver
vds-783625.hosted-by-itldc.com returns Error: open resolver

So I suppose this is /etc/dnsmasq.d/spamhaus

( l liked the AAAA joke :slight_smile: )

Note I have “Enable blocklists for incoming traffic” turned off.

I’m wondering if I just need to wait and keep an eye on email deliveries.

Yunohost requests directly spamhaus server now, so if your config are ok, it could means that your IP is considered as an open resolver (it could be the cas if you open the 53 port).

Thanks … UDP 53 is closed though.

Your dig output is the important bit: Spamhaus is returning an error TXT about the resolver used for the DNSBL query, not a normal listing code for the address being checked. The IPv6 link is therefore not evidence that your IPv4 is listed; it looks like the resolver address Spamhaus objected to. The diagnostic appears to treat that error response as a blocklisting for both the IPv4 and IPv6. Since your local resolver and UDP 53 look right, I’d treat this as a probable false positive and watch actual mail rejection logs; YunoHost ought to distinguish a DNSBL error TXT from a real listing response.

Great, thanks, nice reply.

I suppose a further point is, at the moment, my install is using an SMTP relay … in which case, is this diagnostic relevant ?