hi all,
After upgrading to 2024-4 I noticed my local subnet suddenly was unable to sent emails to the mailcow server.

After a long search, it looks like the location /rspamd/override.d is not checked for a mailcow_networks.map anymore.
That means my local subnet is not concidered local anymore and of course was not allowed to send mail anymore..
Basically leaving all the websites on that subnet not able to send out notification etc…

My “ quick” workaround was to change to modify the options.inc file to look directly to the override.d location but of course that is not a preferred solution…

Anybody else notified something simular maybe?
Any other ideas why it seems to do this?

thx!

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

Upgraded from 2024-2…

A seemingly related problem here:
Mailcow local install behind a wireguard tunnel to a VPS.
Worked flawlessly for years.

Most incoming mails now flagged as spam.
Triggered by the following symbols:
HFILTER_HOSTNAME_UNKNOWN
VIOLATED_DIRECT_SPF
IP_REPUTATION_SPAM (using the IP of the wg tunnel)
R_SPF_FAIL

Seems all these symbols check local settings and not the sender anymore.

After upgrading to 2024-04 from 2024-02 last night our system started receiving emails (shown in the postgres logs) however the emails were not visible to either clients or SoGo. Ended up reverting to the pre upgrade backup.

No one is typing