On Thu, May 14, 2015 at 11:27 PM, Terry Zink <[email protected]> wrote:
> > The Sender header field when present has been defined for > > decades to represent the sending agent! > > Maybe, maybe not. Outlook desktop client shows the Sender: header as > "<sender> on behalf of <5322.from>", but neither Hotmail/outlook.com nor > Gmail do. They just show the 5322.From address regardless of whether or not > there is a Sender: header. This Sender: DMARC fix requires a change in the > way these clients render email. Given the marginal additional benefit to > receiving mailing list traffic that won't implement any of the published > workarounds (not modifying content, fiddling around with Reply-To and From > addresses, changing the From: domain to be the mailing list domain), I > can't see why Gmail or Hotmail would want to make a change like that. I > agree with Murray that it isn't worth pursuing, the cost/benefit ratio > isn't there. > The definition of Sender isn't even what I'm talking about. Its use, not its definition, are what's historically been inconsistent. In particular, as I understand it, it has not historically been the case that all message generating agents that should add Sender, to identify the "actual submittor" (RFC822), have done so. People advocating for keying DMARC on Sender in addition to or instead of >From must then necessarily imply that we should start relying on the greater Internet to begin doing correctly something that has not been done reliably for a long time. -MSK
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
