On Mon, Jul 6, 2020 at 8:43 AM Doug Foster <[email protected]> wrote:
> · Mailing list M sends a message to User A with a request to > ensure that the inbound gateway will accepts its message. The message > contains attachments needed to define and justify the request. I > envision an XML attachment for use with automation, and a text file for > non-automated environments. An XLST file could be used to convert the XML > to TXT, to validate that the XML attachment and the text attachment are > really stating the same thing. > The first thing that comes to mind for things like this is whether and how spammers will try to use this to clear a path to the inbox. How do you know this XML blob is coming from a bona fide list? Anecdotally, spammers were the first to adopt DKIM. This wouldn't be any different. · The email administration then reviews the request and replies to > user and MLM in one of three ways: > This needs to be automatable, or it won't scale to very large operations. I suspect there's virtually zero chance a GMail sized operation will staff up to review requests given the size of their customer base. And once it's automated, there needs to be a strategy for dealing with stale data (e.g., old lists nobody is using anymore), etc. -MSK
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
