On Wed, Jan 15, 2025 at 07:03:23PM +0100, Björn Persson wrote: > > If it's only SPF, then it should be enough to use the forwarding > server's own domain in the SMTP session, like list servers always do. > SPF asks the receiving server to validate the hostname given in > HELO/EHLO and the return address given in MAIL FROM in SMTP. A correct > SPF implementation will only look at the SMTP envelope, not the email > header.
Note that this is again just an alias, there's no other processing. So, it goes: pers...@a.com -> (mimecast) -> fedoraproject.org alias is expanded fedoraproject.org -> pers...@b.com so if a.com has a 'reject' rule, and b.com actually pays attention to that it will reject/do whatever it wants with the email from pers...@a.com. > The problems usually arise when the sender has a DMARC rule that forbids > forwarding and the recipient enforces DMARC, because DMARC imposes > requirements on the From field of the email header. That, I believe, is > when this mailing list rewrites the From field, and the forwarding > alias server would have to do the same. You can tell which posters have > strict DMARC rules by the "via devel" that gets appended to their names. Right. I don't know of any existing software setup that does this, so one would have to be written. :) (not me). kevin
signature.asc
Description: PGP signature
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
