On Friday, March 29, 2013 1:17 AM [GMT+1=CET],Michael Adkins wrote: > We use responsys (and a couple of other 3rd party senders) for dmarc > protected domains without issue. It's important to remember that this > only creates a problem if the domain in question is actually being > abused. It's easy to publish dmarc records and just collect data on > them to > determine if you need to go through the effort of aligning the > identifiers > before you go through the effort of aligning the identifiers. No one > should start with the assumption that they need a reject policy. If > you > do, then there are several options for how to proceed. > > We covered the issues for 3rd party senders in the maawg training > videos - > http://www.maawg.org/activities/training/dmarc-training-series >
Very interesting video: http://www.maawg.org/activities/training/dmarc-video-6 So far, however, in the current state of the affairs it looks like a lot of "educational effort" will need to go around to get domain owners to "tune" some of their DNS resource records in order for third parties to which they outsource sending email in their behalf to do such email-sending in a DMARC-authenticated and aligned way. Perhaps creating a subdomain of the owner's domain, and handing control of that subdomain over to the outsourced email marketing company will be the way to go in an easily-automated way that causes the least of process overhead for the domain owner. The "organizational domain" concept of DMARC together with DMARC's "relaxed mode" I think will be of great help for this approach. Regards, J. Gomez _______________________________________________ dmarc-discuss mailing list [email protected] http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
