Email forwarding failed

maxtomain

I would like to ask, when I try to forward a verification code sent by someone else to another user, there is one email that cannot be forwarded
(error code: 550 5.7.1 [2600:1901:101::1] Messages missing a valid Message-ID header are not accepted. For more information, go to https://support.google.com/mail/?p=RfcMessageNonCompliant and review RFC 5322 specifications. 586e51a60fabf-2c6712cf6e7si9825318fac.204 - gsmtp)
Except for the specified email, all other emails can be forwarded normally，That’s strange!!!!

esackbauer

How are you forwarding? In SOGo manually? Or with a rule without rewriting the sender address to your own address?

maxtomain

Manually forwarding works fine, but when forwarding using a rule, it fails (only the verification email results in a failure)

esackbauer

I thought so. The rule should rewrite the sender address. If you e.g. forward a mail from gmail.com via rule, then it keeps its gmail.com sender address, but the recipients mailserver sees your mail server IP address, which is not part of gmails SPF and DKIM.
Automated rule based forwarding should be avoided at all, because of such problems. Even if there exists something like SRS (Sender rewrite Scheme), it is not a guarantee that the forwarded mail will reach the recipient.

maxtomain

esackbauer So, does that mean the email can’t use automatic forwarding rules? Or is there an SRS package available for use with Mailcow? (I couldn’t find built-in SRS in Mailcow, and I only found this article: https://nowhere.dk/articles/implementing-srs-with-mailcow/. I’m not sure if it’s still usable, or if there are any newer supported packages available?

esackbauer

It seems it does not work for gmail as receiving mail servers. You need to check your workflow if there is no better alternative solution than forwarding such mails.