Spamhaus incorrect operation
recoilstv opened this issue · comments
Hi! When checking the system status, I receive the following message: This domain is listed in the Spamhaus Domain Block List (code 127.255.255.254), which may prevent recipients from receiving your mail. See http://www.spamhaus.org/dbl/ and http://www.spamhaus.org/query/domain/mydomain. The same situation happens with my IP. But there are no problems when checking the status by the link. Because of this, I can't send and receive mail. After the reboot spamassassin, spampd & postfix sending, but not receiving work again.
My box was doing the same thing, and it has suddenly stopped. How about yours?
Hi. I removed all the Spamhaus settings from the Postfix configuration and wrote on the product support forum
i had this a few times.
Spamhaus support will remove you from their list if its a false positive (which occurs too often imho). There is a form for that in the links you showed. Its done in a few hours, but still.... annoying
i had this a few times. Spamhaus support will remove you from their list if its a false positive (which occurs too often imho). There is a form for that in the links you showed. Its done in a few hours, but still.... annoying
I wrote above that there are no problems when checking the status of the link on the Spamhaus website.
yes, this is a problem. My box is rejecting all emails as spam, since it can no longer properly get spamhaus info.
This might happen when you're not using the Mail in a box built-in DNS resolver. Spamhaus will return error codes 127.255.255.254 and 127.255.255.255 for public/open resolvers, or when a user makes an excessive number of queries.
Did you change anything to the DNS settings of the box?
However, the default set up had 1.1.1.1 as DNS server.
That should not be the case. But perhaps your VPS provider overwrites the MiaB configuration? (it has happened before) How did you deploy this installation.
Changing to 127.0.0.1 fixed the issue temporarly
Why temporarily?
However, the default set up had 1.1.1.1 as DNS server.
That should not be the case. But perhaps your VPS provider overwrites the MiaB configuration? (it has happened before) How did you deploy this installation.
I ran into the issue again. It does not seem to be my cloud provider overwriting the setting, but rather the setting not being applied successfully during setup. I was able to resolve this with creating /etc/resolvconf/resolv.conf.d/head and applying it with resolvconf. After restarting resolved everything worked as expected. Maybe this is about Ubuntu changing how DNS servers are configured, or maybe also about different networking setups used by VPS providers?