I think I’ve identified a misconfiguration related to Spamhaus.
We’ve repeatedly struggled to delist from Spamhaus, and it may be due to how the Mailcow script handles mailboxes.
The script treats inboxes as virtual mailboxes, which forces Postfix to treat the domain like a third-party. As a result, you can’t set your domain as a local destination.
This causes Spamhaus to score internal emails the same way it scores external ones. For example, when a mailer daemon sends bounce messages, it can trigger a burst of “spammy-looking” traffic, prompting Spamhaus to flag the server’s IP — it’s own IP.
I’m not sure if this is the root cause, but it seems plausible.
Prost!
i believe it’s necessary to bypass current machine’s ip and domain in dnsbl list by default.
i believe it’s necessary to bypass current machine’s ip and domain in dnsbl list by default.
i believe it’s necessary to bypass current machine’s ip and domain in dnsbl list by default.
i believe it’s necessary to bypass current machine’s ip and domain in dnsbl list by default.