In article <by5pr13mb29998094418c8a6c25902569d7...@by5pr13mb2999.namprd13.prod.outlook.com> you write: >To put it another way: > > * assist...@firstbrand.com is organizing a meeting for > execut...@secondbrand.com > * assist...@firstbrand.com sends out a calendar invite from their own > messaging client, using >execut...@secondbrand.com in the From: field > * The resulting message uses execut...@secondbrand.com in the friendly > From: field, but firstbrand.com in the >SMTP MAIL FROM domain, so the headers are no longer aligned for SPF. > * Both firstbrand.com and secondbrand.com are set to DMARC p=reject. > * Messages like this are then rejected by receivers that validate DMARC > results.
This sounds like an excellent use case for Dave's draft-crocker-dmarc-sender proposal. The canonical example of different From and Sender is exactly this: Sender is an assistant working for and sending mail for From. R's, John _______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
