Similar message reported on Pyzor (https://www.pyzor.org)

Hello everyone!

I’m facing this problem


curl -sSL https://7j.gg/chksph2 | bash -s --
Test 01: Request ignored by Spamhaus or DNS Resolver timed out
Test 02: Request ignored by Spamhaus or DNS Resolver timed out
Test 03: Request ignored by Spamhaus or DNS Resolver timed out
Test 04: Request ignored by Spamhaus or DNS Resolver timed out
Test 05: Request ignored by Spamhaus or DNS Resolver timed out
Test 06: Request ignored by Spamhaus or DNS Resolver timed out
Test 07: Request ignored by Spamhaus or DNS Resolver timed out
Test 08: Request ignored by Spamhaus or DNS Resolver timed out
Test 09: Request ignored by Spamhaus or DNS Resolver timed out
Test 10: Request ignored by Spamhaus or DNS Resolver timed out

Result is bad, Spamhaus is blocking/ignoring your current DNS Resolver 127.0.0.53{}

IP not on blacklist

Spf aligned

Dkim aligned

Dmarc aligned

I tried to follow some steps found here on the forum,

I’m using

 Static hostname: server.xxxxxxx.xx
       Icon name: computer-vm
         Chassis: vm
  Virtualization: kvm
Operating System: Ubuntu 22.04.5 LTS               
          Kernel: Linux 5.15.0-138-generic
    Architecture: x86-64
 Hardware Vendor: QEMU

But here there is no such file in /etc/resolvconf/resolv.conf.d/head

Now, can anyone help?

Try to use some real content instead test message or what you have send

1 Like

@eris

In fact, in the body of the test email and title I had only put test.

I did another test and with a more elaborate message and it didn’t give the PYZOR notification, thanks!

But what about the result curl -sSL https://7j.gg/chksph2 | bash -s --
Why is it giving this return?

curl -sSL https://7j.gg/chksph2 | bash -s --
Test 01: Request ignored by Spamhaus or DNS Resolver timed out
Test 02: Request ignored by Spamhaus or DNS Resolver timed out
Test 03: Request ignored by Spamhaus or DNS Resolver timed out
Test 04: Request ignored by Spamhaus or DNS Resolver timed out
Test 05: Request ignored by Spamhaus or DNS Resolver timed out
Test 06: Request ignored by Spamhaus or DNS Resolver timed out
Test 07: Request ignored by Spamhaus or DNS Resolver timed out
Test 08: Request ignored by Spamhaus or DNS Resolver timed out
Test 09: Request ignored by Spamhaus or DNS Resolver timed out
Test 10: Request ignored by Spamhaus or DNS Resolver timed out

Result is bad, Spamhaus is blocking/ignoring your current DNS Resolver 127.0.0.53{}

Seems you are using an open resolver and Spamhaus is ignoring the requests to check IPs in their DNSBL zen.spamhaus.org

Show the output of this command:

resolvectl status
1 Like

@sahsanu

resolvectl status

Global
         Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
  resolv.conf mode: stub
Current DNS Server: 8.8.8.8
       DNS Servers: 8.8.8.8 8.8.4.4

Link 2 (ens18)
    Current Scopes: DNS
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 8.8.8.8
       DNS Servers: 8.8.8.8 8.8.4.4

Ok, Spamhaus is ignoring requests from Google’s public DNS servers. This won’t cause any problems for the emails you receive, but malicious IPs listed in the Spamhaus database will not be blocked.

Check this post to see a few options to fix this issue:

Hi @sahsanu

I did what you suggested, but out of the 4 options I chose the fourth option, I created the record in…

I edited /etc/exim4/dnsbl.conf
I edited /etc/exim4/exim4.conf.template
I restarted exim

But I still get the same result
Result is bad, Spamhaus is blocking/ignoring your current DNS Resolver 127.0.0.53{}

The script doesn’t check whether you’re using a DQS key, so if you’ve already added it, you should be fine. If you’d like to verify, use the following (replace HereYourDQSKey with your actual DQS key… but make sure not to share it with anyone):

dig txt +short 4.0.0.127.HereYourDQSKey.zen.dq.spamhaus.net

If you see this output, you are good:

"Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4"

If you want to check the previous situation:

dig txt +short 4.0.0.127.zen.spamhaus.org

If you see no output, Spamhaus is ignoring your dns resolver.

As I said, if DQS Key test works, all is ok.

@sahsanu

dig txt +short 4.0.0.127.HereYourDQSKey.zen.dq.spamhaus.net
"Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4"

didn’t worry at all dig txt +short 4.0.0.127.zen.spamhaus.org

Can this problem below affect email delivery?
Result is bad, Spamhaus is blocking/ignoring your current DNS Resolver 127.0.0.53{}

Could affect receiving mails but not sending them. As you already configured Exim to use Spamhaus with the DQS key you shouldn’t be worried about it.

@sahsanu

I don’t understand, because my IP is clean, ptr, dns, mx, spf, dkim, dmack all aligned and email goes to spam

Meu unico problema Name Servers are on the Same Subnet

If you can give me any suggestions I would be grateful.

It depends on each mail service; they all have their own rules.

Some will send you to spam if your domain is new, others if they’ve received only a few emails from you, if any user has marked your messages as spam, if your hosting provider has a lot of reports on their IP ranges (even if your specific IP isn’t on any blocklists), some TLDs are more likely to be flagged as spam, or if the stars didn’t align in the right order when the moon was in its last quarter, etc.

1 Like