ALL emails suddenly get quarantined. Karma records records ALL IP addresses as "Bad" connection

[o9Isd kS$ds]

1. Issue:

   1. As of Aug 15, 2021, ALL emails suddenly get quarantined. Karma records records ALL IP addresses as "Bad" connection. No settings have been changed in 2 years!

2. Expected result:

   1. Obviously, emails must be delivered, not quarantined.
   2. “Quarantine” functionality should be shut down if it misbehaves like this. Where is this done????

3. Background:

   1. Server was running well for 2 years. Sometime in mid-August 2021, none of email were being delivered. Logging into admin webUI, all emails were being quarantined, and all connecting IP addresses, including mails from google, had “BAD” connections (Blacklist/Whitelist->Karma Records).

4. Working Workaround:

   1. The ONLY workaround that works is Whitelisting all incoming IP addresses. This is not only impractical, but also dangerous.

5. Failed workaround:

   1. System Settings-> Spam & Virus checks → DISABLING “Spam check” and”Antivirus check” DOES NOT solve quarantine problem.

6. From user manual, It is unclear where quarantine “settings” are located, what triggers them, and how to completely shut it down, in case it causes the aforementioned issue.

‌

[Equipe Ideacorp]

Hi, did you happen to update to the newer versions?

[o9Isd kS$ds]

Yes. Current Version 2.3.4

[Monnier]

I have the same issue, has it been solved?

[zdfgfh]

Same problem, tried different versions and backups. Disabling quarantine doesn’t fix as it just bounces all incoming mail.

[Monnier]

This problem seems quite old, it is mentioned here too.

https://forums.unraid.net/topic/69507-support-posteio-free-version/

I couldn't continue to use it, I changed my mail server solution

[Nicolas VIOLLIN]

Hello !

Same problem ocurs here… All worked fine for the last 3 years and suddenly this week all emails are quarantined…

Any workaround ?

[Monnier]

I had implemented a workaround. I whitelisted 0.0.0.0/0 to allow everything. But it's not very clean

[zdfgfh]

Thanks for the workaround I’ve implemented it temporarily while I look at alternatives. It’s a shame as when it worked it worked well. What have you moved to? Was looking at maybe mailinabox.

[Clément VILLISEK]

Hello.

I am also facing the exact same issue since a few days. My mail server wasn’t up to date when it began, and even updating it to the latest version doesn’t fix the issue.

Thank you for the workaround!

[Monnier]

I moved to docker-mailserver, everything works fine.

https://docker-mailserver.github.io/docker-mailserver/edge/

after several tests with poste.io, I realized that the problem probably comes from the DNSBL function with zen.spamhaus.org because I have the same problem when I activate it on Docker-mailserver, all incoming mails are rejected.

[zdfgfh]

Thanks, I came to the same conclusion about spamhaus. I tried whitelisting 0.0.0.0/0 earlier but it was causing issues.

I’ve been troubleshooting this with the poste.io guys (they’ve been very helpful) and it turns out the problem occurs as spamhaus doesn’t play nice with public DNS servers (e.g. 1.1.1.1). Changing to my ISP’s DNS server fixes the erroneous karma scoring and things are back to normal! I’m unsure why this has only recently become a problem but it looks like it is now fixed for my setup.

[Monnier]

I tested your solution but the problem is still there, but I see my ISP's DNS responding.I don't understand, I think there is an internal problem at spamhaus.

I disabled the DNSBL and I work without for the moment

[Michal Kalita]

Hi, I have same problem with a lot of emails in quarantine ( about 95% )
RSPAMD score is good, but email is in quarantine. I don’t change any configuration, it just stop works.

[Monnier]

apparently the 2.3.9 update resolves the issue.

you can test

[SH]

• 2.3.9 solve this, but this is an half-way solution
• the main problem is that you are most likely using public DNS resolver AND Spamhaus started refusing to work with that, see https://www.spamhaus.org/news/article/807/using-our-public-mirrors-check-your-return-codes-now
• return codes was fixed latest version BUT spamhaus blacklist is not working

(additional test for using public mirror needs to be done, document for implementing Spamhaus DQS also)