Re: DMARC -> CERT?

[Christopher Morrow <morrowc.lists () gmail com>]

On Mon, Apr 14, 2014 at 4:44 PM, Scott Howard <scott () doc net au> wrote:
> On Mon, Apr 14, 2014 at 1:39 PM, Christopher Morrow
> <morrowc.lists () gmail com> wrote:
> > On Mon, Apr 14, 2014 at 4:34 PM, Matthias Leisi <matthias () leisi net>
> > wrote:
> > > They could have communicated, as in "listen folks, we are going to make
> > > a
> > > critical change that will affect mailing lists (etc...) in four weeks
> > > time".
> >
> > communicated it where?
>
>
> "The Internet".

I was trying, really, to be not-funny with my question.

if you're going to do something that has the potential to affect (say,
for example) email to a wide set of people, most of which are NOT your
direct users, how do you go about making that public?

'the internet' isn't really a good answer for 'how do you notify'.
Doug's note that: "email mailops" is good... but I'm not sure how many
people that run lists listen to mailops? (I don't ... i don't run any
big list, but...)

I also wonder about update cycles for software in this realm? and for
very larger list operators there's probably some customization and
such to hurdle over on the upgrade path, eh? so how much leadtime is
enough? how much is too much? 1yr seems like a long time - people will
forget, 1wk doesn't seem like enough to avoid firedrills and
un-intended bugs.

> A blog entry and a post to a few key relevant mailing lists would have

specifically which mail-lists?

> resulted in the message spreading far better than it was.  There's no way
> that they could have communicated it to every mailing list admin on the
> planet, but they could have at least given a heads-up to some major parts of
> the community.
>
> The great thing about the Internet is that if it's important enough to be
> shared, you don't need to try too hard to make that happen - others will
> look after it for you.  But you need to make the effort to get it started,
> and Yahoo didn't do that here (or at least, they did, but they did it by
> actually making the change by which time it was too late!)
>
>   Scott