On Tue, Apr 14, 2015 at 3:41 PM, Terry Zink <tz...@exchange.microsoft.com> wrote:
> 1. For Hotmail, every mailing list that our users are signed up for would > result in a new DNS entry. How do we manage the lifecycle around that? > Should we automate its addition? Should we automate its removal? Do we > delay email before the DNS entries are published? Should we thereby bypass > the change review process? If so, how do we audit what's going in and > what's coming out of the Hotmail zone? > > 2. For Office 365, we can't publish DNS entries for most of our customers. > We could tell them what to publish but I guarantee you almost none of them > would for every single mail list their users signed up for, if they had to > do it every day. Most of them probably wouldn't even do it once. > > That's the part that doesn't scale. +1. The mechanism of generating DNS records is not the issue; we even have an RFC that shows how that could be done in theory. It's the processes themselves that simply won't scale or would fail to thrive. -MSK
_______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
