On Fri, Mar 31, 2023 at 2:32 PM Hector Santos <hsantos= [email protected]> wrote:
> Is there a specification for rewriting the 5322.From to help resolve DMARC > p=reject redistribution problems? > RFC 7960 isn't a specification for rewriting 5322.From per se, but section 4.1.3.1 discusses the topic of rewriting that header, including this text: Another option for ReSenders is to rewrite the RFC5322 <https://www.rfc-editor.org/rfc/rfc5322>.From header field address to a locally controlled address that will be forwarded back to the original sender (subject to its own ReSender forwarding mitigations). https://www.rfc-editor.org/rfc/rfc7960.html#section-4.1.3.1 > What is the logic the IETF.ORG list using? > > I'm guessing it's: if (DMARC policy of poster's email domain exists and is not p=none) then rewrite 5322.From to [email protected] fi For example: $ host -tTXT _dmarc.isdg.net _dmarc.isdg.net descriptive text "v=DMARC1; p=reject; atps=y; rua=mailto: [email protected]; ruf=mailto:[email protected];"; Leads to: On Fri, Mar 31, 2023 at 2:32 PM Hector Santos <hsantos= [email protected]> wrote: The rewriting that the IETF is doing seems to be from the same neighborhood as the Sender Rewriting Scheme used sometimes for 5321.From rewriting to mitigate SPF failures - https://www.libsrs2.org/srs/srs.pdf -- *Todd Herr * | Technical Director, Standards and Ecosystem *e:* [email protected] *m:* 703.220.4153 This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
