On Saturday, April 06, 2013 2:20 AM [GMT+1=CET], Douglas Otis wrote: > There has been some discussion regarding often violated third-party > limitations of DMARC policy. A modified version of > http://tools.ietf.org/html/rfc6541 where DMARC is used to signal ATPS > support rather than inclusion of 'atps' tags within the DKIM > signature can offer fewer use constraints. > (...) > For example say some social network wishes to protect users messages > using DMARC while allowing participation with various third-party > relay services, such as well managed mailing-lists. ATPS provides a > means for DMARC domains to make explicit exceptions and to react > quickly when a problem is reported.
Will that mean that for every mailing list that your users subscribe to, you would have to update/amend your DMARC DNS RR to declare the Organizational Domain on which said mailing list is hosted? If so, I see it as not very scalable, error prone, intensive in human labour, and a reactive solution instead of a proactive one (i.e, only after you discover your users have subscribed to a mailing list, and DMARC is causing them pain, you enter the picture and amend your DMARC DNS RR to solve the problem which already has happened). On the other hand, if I am misunderstanding your proposal, please disregard this message. 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)
