On Saturday, October 25, 2014 5:57 PM [GMT+1=CET], Dave Crocker wrote: > On 10/25/2014 12:34 PM, J. Gomez wrote: > > On Saturday, October 25, 2014 3:38 AM [GMT+1=CET], Hector Santos > > wrote: > > > > > DMARC is a DKIM Policy Framework. According the marketing, it has > > > gain widespread adoption especially among your list users > > > domains. Isn't why you are here, to stop it? > > > > If by "widespread adoption" you mean that major mailbox providers > > (Gmail and others) are ignoring the Sender's DMARC policy (Yahoo, > > AOL and others), then yes: DMARC defines a DKIM policy which has > > widespread adoption. > > DMARC defines DMARC-related 'policies'. > > It does not affect DKIM in any way. It is an overlay to DKIM and/or > SPF use.
DMARC defines DMARC-related 'policies' which are an overlay on DKIM, which to me could be also aptly phrased as "DMARC creates a policy framework for DKIM", and more succintly "DMARC is a DKIM Policy Framework". Yes, DMARC does not change DKIM de-iure. But also, yes, DMARC does bring POLICY to DKIM. The truth here is that DMARC is going to be a de-facto DKIM 2.0. And when I say "de-facto", I mean in production systems, on the trenches, in the muddy world of reality where support costs do exist and ivory towers are far in the distance and rest high away from all the mudd. Regards, J. Gomez _______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
