False positive on SpamHaus
-
@p44 Removing the entry there only stops IP addresses of incoming mail from being checked against the blocklist. It does not affect the email configuration checks, and there is apparrently no way to override this at the moment.
-
We really need some more insights about this issue since reproduction is very hard to impossible.
Disclaimer If you are not comfortable posting your details here, I just enabled that everyone in the forum can send me private messages.
Anything not related to this topic in my private messages will be ignored.
To everyone affected, please provide us with the output of the following command from your Cloudron server:
cloudron-support --send-diagnosticsAdding to that, we could need the domain that you are using for mail.
Furthermore, the more detailed you can describe your system and how you use it, the better we can try to reproduce this to find a solution. -
@james, I sent you details via chat yesterday. Or did you mean something else by "private message"?
-
I just noticed that my Cloudron instance is experiencing similar symptoms: my Email status settings says that my IP is blocked by SpamHaus Zen, but when I put my IP into SpamHaus Zen's checker it comes up clean.
It's a bit unclear at the moment if there is a resolution to this or not?
-
I just noticed that my Cloudron instance is experiencing similar symptoms: my Email status settings says that my IP is blocked by SpamHaus Zen, but when I put my IP into SpamHaus Zen's checker it comes up clean.
It's a bit unclear at the moment if there is a resolution to this or not?
@thetomester13 are you on a vps or personal cloud?
-
I just noticed that my Cloudron instance is experiencing similar symptoms: my Email status settings says that my IP is blocked by SpamHaus Zen, but when I put my IP into SpamHaus Zen's checker it comes up clean.
It's a bit unclear at the moment if there is a resolution to this or not?
Hello @thetomester13 please read the post I've made here => https://forum.cloudron.io/post/107766
-
After several years running Cloudron, this issue made me shut down my server and find another hosting for my needs. I have had several issues in the past, and the support team was always willing to help, and I am very thankful for that. But this Spamhaus problem affected my private and business communication for several weeks with no foreseeable solution. I believe that I will use Cloudron for some less critical applications in the future.
-
After several years running Cloudron, this issue made me shut down my server and find another hosting for my needs. I have had several issues in the past, and the support team was always willing to help, and I am very thankful for that. But this Spamhaus problem affected my private and business communication for several weeks with no foreseeable solution. I believe that I will use Cloudron for some less critical applications in the future.
-
After several years running Cloudron, this issue made me shut down my server and find another hosting for my needs. I have had several issues in the past, and the support team was always willing to help, and I am very thankful for that. But this Spamhaus problem affected my private and business communication for several weeks with no foreseeable solution. I believe that I will use Cloudron for some less critical applications in the future.
@neki said in False positive on SpamHaus:
After several years running Cloudron, this issue made me shut down my server and find another hosting for my needs. I have had several issues in the past, and the support team was always willing to help, and I am very thankful for that. But this Spamhaus problem affected my private and business communication for several weeks with no foreseeable solution. I believe that I will use Cloudron for some less critical applications in the future.
This kind of situation clearly worries me about hosting my email on Cloudron and is the kind of concern I had expressed few weeks ago to people hosting their email on Cloudron. Ref: https://forum.cloudron.io/post/107104
And just when I started to be less worried, this SpamHaus issue popping up and being such a blocker is quite concerning
-
@neki If you are experiencing problems with inbound mail being rejected, have you tried just removing Spamhaus from the list of DNSBL checks?
@ccfu No, I haven't tried removing Spamhaus from the list of DNSBL checks. However, I don't think it would help in my case. My IP address wasn't listed in Spamhaus, and the issue seemed to be related to a misconfiguration warning in Cloudron, even though everything was set up correctly. So I doubt that disabling Spamhaus would have made a difference.
-
@neki said in False positive on SpamHaus:
After several years running Cloudron, this issue made me shut down my server and find another hosting for my needs. I have had several issues in the past, and the support team was always willing to help, and I am very thankful for that. But this Spamhaus problem affected my private and business communication for several weeks with no foreseeable solution. I believe that I will use Cloudron for some less critical applications in the future.
This kind of situation clearly worries me about hosting my email on Cloudron and is the kind of concern I had expressed few weeks ago to people hosting their email on Cloudron. Ref: https://forum.cloudron.io/post/107104
And just when I started to be less worried, this SpamHaus issue popping up and being such a blocker is quite concerning@SansGuidon James (@james) asked for more info from people having this issue so he can help, but I was the only one who responded. Not sure why ... maybe it affects only a few users and they do not use their email servers for important stuff, I don't really know. To me, it was a nightmare knowing that some messages for me were not delivered (not even to the spam folder).
-
@ccfu No, I haven't tried removing Spamhaus from the list of DNSBL checks. However, I don't think it would help in my case. My IP address wasn't listed in Spamhaus, and the issue seemed to be related to a misconfiguration warning in Cloudron, even though everything was set up correctly. So I doubt that disabling Spamhaus would have made a difference.
@neki The misconfiguration warning is for your IP and has no relevance for incoming mails. That warning is being shown because Spamhaus is not reponding correctly to the request from Cloudron and Cloudron is incorrectly interpreting that as your IP being blocklisted. It is nothing more than a display error though and should be fixed in the next release.
If you are seeing incoming mails rejected due to Spamhaus listing then this is due to the DNSBL checking. The error may well be with Cloudron and how Spamhaus reports are interpreted, but that will be resolved if you deactivate the checks.
@SansGuidon Had you removed Spamhaus from the DNSBL checks? I think the issue is (at least partly) to do with changes in the way Spamhaus processes queries (I noticed a lot of errors in the logs before deactivating Spamhaus altogether) and the way Cloudron interprets the results when errors are thrown.
I have two Cloudron servers, both running version 8.3.2, but one on Ubuntu 22.04, the other on Ubuntu 24.04. Interestingly, the server running on 24.04 does not show the (false) email configuration error, but the one on 22.04. regularly does. As already mentioned, however, that is just an icorrect message and has no affect at all on deliverability as that will depend only on the receiving mailserver.
