At least the big companies like GMail never complained about it, the Authenticated Received Chain (ARC) always passes without errors, even for forwarding. :-)
> Am 05.02.2025 um 15:28 schrieb Geert Hendrickx via Postfix-users > <postfix-users@postfix.org>: > > On Wed, Feb 05, 2025 at 14:58:48 +0100, Ömer Güven via Postfix-users wrote: >> My solution does completely remove the Received header, so that the >> next-hop adds an appropriate one, usually pointing to the sending MX‘ >> ip address. > > > Which is also not RFC 5321 compliant, just not visibly so :) > > >> It is still a valid Received header, just like the ones added by >> submission via sendmail(1). Example (current unmodified Postfix): >> >> Received: by <hostname> (Postfix, from userid 1000) >> id 2408492CB80; Wed, 22 Jan 2025 01:04:55 +1100 (AEDT) >> >> See https://datatracker.ietf.org/doc/html/rfc5322#section-3.6.7 >> which covers non-SMTP cases by essentially saying any list >> of syntactically valid pairs is fine. The submitted message >> is presented as not arriving via SMTP, and so SMTP (RFC 5321) >> rules don't apply. > > > Ok, that makes sense. As long as it's RFC 5322 compliant (which indeed > defines a less strict format), it's OK for the outside world. And what > happens "behind" the border MTA, is internal business. > > Thanks Viktor. > > > Geert > > > _______________________________________________ > Postfix-users mailing list -- postfix-users@postfix.org > To unsubscribe send an email to postfix-users-le...@postfix.org
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
