mailcow Unauthenticated Relaying

olli1411

Hello everyone!

I have configure my postfix like this configuration here:
https://docs.mailcow.email/manual-guides/Postfix/u_e-postfix-unauthenticated-relaying/

I have added my second mailserver (behind mailcow) to the mynetworks and restart the container.

After sending out emails i get the following bounce back from mailcow:

Remote Server returned ‘554 5.7.1 This message does not meet our delivery requirements’

So I also stored the IP in the mailcow gui within the forwarding hosts setting. If I switch off the SPAM filter with this option, I can now send e-mails.

However, there is a problem, all outgoing emails from this system are then NO longer DKIM signed, why?

In addition, the emails then have this strange X header:

X-Rspamd-Pre-Result: action=no action; module=Unknown lua; ip matched with forward hosts

It wasn’t there before the update either!

If I switch on the SPAM filter, the e-mail is apparently treated like an external e-mail and rejected.

This has only occurred since the last update. Any ideas? Docker is already up to date.

Is it possibly a bug?

spanguel

Hey, i just ran into the same issue. i followed the docs to allow unauth relay for 2 subnets and got the same message.
After adding the host into forwarding hosts i came to the same result with those mails missing dkim.

i then added my networks to /data/conf/rspamd/custom/mailcow_networks.map
now those relayed mails get dkim again.

But those Settings are overwritten after restarting the rspamd container with the IPV4 and IPV6 settigns from mailcow.conf

any clue on how to make that persistant?

esackbauer

See here, you need to edit the options.inc, not the mailcow_networks.
https://community.mailcow.email/d/3613-dkim-signing-lua-dkim-toolslua195-mail-is-ineligible-for-signing/10