False positive on SpamHaus
-
Since the update to 8.3.2 (on Ubuntu 24) I am seeing these false positives as well. Nothing has changed with the network settings or DNS. I know it is ultimately just a cosmetic problem, but it would be nice to be able to deactivate this check as it serves no real purpose in my opinion.
-
Since the update to 8.3.2 (on Ubuntu 24) I am seeing these false positives as well. Nothing has changed with the network settings or DNS. I know it is ultimately just a cosmetic problem, but it would be nice to be able to deactivate this check as it serves no real purpose in my opinion.
@ccfu I can not agree on deactivate - the purpose is very useful. I would rather have it working properly!
-
@ccfu I can not agree on deactivate - the purpose is very useful. I would rather have it working properly!
If it worked properly that would of course be better
If only one blocklist is being checked (Spamhaus) its purpose is, in my view, rather limited. In any case a failed check due to a connection error should not cause a notification that the mailboxes are not set up correctly and these mailboxes to be showing as red in the list.
Edit: Connection errors happen with correct configuration when an ISP's DNS gets temporarily blocked by the DNSBL server. That seems to be my issue at the moment. In such cases I would like to be able to deactivate the check (even temporarily, for example 24 or 48 hours).
-
Im having the same false positive issue. Do I have to read through this whole thread and the other one or is there a simple fix/do I just need to wait for an update?
-
-
I have a task to make this check more "stable" for next release. Currently, it just shows the message on a single failure . I will fix the code to make it show when the error is more persistent (i.e over several failures or something like that).
@girish That would be a big help for sure, but would it not make more sense to differentiate between connection failure and actual confirmed presence on the blocklist?
At the moment it seems to check every 30 minutes and if the DNS server has been blocked (e.g. for overuse of queries) this is likely to persist for 24 - 48 hours at least.
-
@girish That would be a big help for sure, but would it not make more sense to differentiate between connection failure and actual confirmed presence on the blocklist?
At the moment it seems to check every 30 minutes and if the DNS server has been blocked (e.g. for overuse of queries) this is likely to persist for 24 - 48 hours at least.
@ccfu the check is only once a day - https://git.cloudron.io/platform/box/-/blob/master/src/cron.js?ref_type=heads#L113 . But yeah, the code should ideally say "rate limited" , "connection timed out" . Some proper error messages. Thing is something has changed in SpamHaus recently and this is why many are hitting it . I have to test in depth to figure what the exact problem is. I just put a note here saying I will look into the issue for next release
-
Thanks, @girish
FYI, in the notification it says "Email Status is checked every 30 minutes. See the troubleshooting docs for more information." This appears to be incorrect then. The notification does indeed only come once every 24 hours. -
@girish said in False positive on SpamHaus:
@ccfu good catch. I removed that misleading message, thanks
I think your change just render obsolete the code comment saying to remove the duration in notification but I'm not sure
https://git.cloudron.io/platform/box/-/blob/master/src/cron.js?ref_type=heads#L113 -
@girish said in False positive on SpamHaus:
@ccfu good catch. I removed that misleading message, thanks
I think your change just render obsolete the code comment saying to remove the duration in notification but I'm not sure
https://git.cloudron.io/platform/box/-/blob/master/src/cron.js?ref_type=heads#L113 -
Grrrr, I got the same issue now - Cloudron says in blacklist, Spamhaus says not.
Trying to get my head around this long thread.EDIT : errr, so TL;DR is nothing we can do and Cloudron will fix it “sometime” ?
Maybe I read too fast, but that’s my takeaway at the moment ... -
Grrrr, I got the same issue now - Cloudron says in blacklist, Spamhaus says not.
Trying to get my head around this long thread.EDIT : errr, so TL;DR is nothing we can do and Cloudron will fix it “sometime” ?
Maybe I read too fast, but that’s my takeaway at the moment ...@timconsidine That's about right, yes.
-
Hello, I seem to have the same issue. My email contacts are getting error message from their mailservers, because their messages to me are getting rejected, falsely marked as positives.
@tadeas said in False positive on SpamHaus:
Hello, I seem to have the same issue. My email contacts are getting error message from their mailservers, because their messages to me are getting rejected, falsely marked as positives.
That sounds like a completely different issue to me.
-
SpamHaus connections from Cloudron are not at all reliable at the moment. As @girish wrote, something seems to have changed recently at SpamHaus.
There are two issues that would appear to both be caused by the same problem (refused connections to the SpamHaus servers): the false positive reports that the IP is on the blocklist and the lack of blocklist checking of incoming mails resulting in mails from IPs that are on the blocklist not being identified as such. That could explain an increase in the amount spam getting through, though SpamAssassin rules should still filter a lot of these. SpamAssassin cannot delete incoming mails but can at least make sure they go straight to the Spam folder.
There are other blocklists for incoming mail. I have had good results with Abusix, for example. It is not possible to set a different blocklist in the mail configuration checks though.
-
@ccfu I exactly followed your advice: removed SpamHaus and added SpamAssassin rules https://forum.cloudron.io/post/105256 by @d19dotca
