Re: Mailing lists - assumptions

> -----Original Message-----
> From: Theodore Ts'o [mailto:[email protected]]
> Sent: Friday, April 18, 2014 5:09 PM
> To: MH Michael Hammer (5304)
> Cc: Pete Resnick; [email protected]
> Subject: Re: [ietf-822] Mailing lists - assumptions
> 
> On Fri, Apr 18, 2014 at 09:04:06PM +0000, MH Michael Hammer (5304) wrote:
> >
> > There is a distinct difference between the two approaches. If an
> > organization I support, whether they do it knowingly or because the
> > person or organization that manages their mailing lists decides to
> > make such a decision (without advising management) to send me a nasty
> > email intended to coerce me to do anything (doesn't have to be just
> > about switching mailbox providers), of course I am going to withdraw
> > support. I would fully expect others to feel along the lines I do. To
> > be blunt, people (end users) don't particularly care about your
> > impossible situation as a list administrator. It is your job to figure
> > out the least intrusive way of dealing with the situation and of
> > course, to communicate with the impacted users politely and where
> > possible providing them options. This is not specific to the Yahoo
> > DMARC implementation issue, that is the real world. You are focused on
> > solving your problem (and crusade) and not necessarily theirs.
> 
> All of the short-term workarounds will negatively impact the yahoo.com user
> somewhat.  (It is because of the negative impact that I think it's best if the
> workaround is deployed only if the recipient has a DMARC p=reject policy, as
> opposed to being inflicted on all of the mailing list recipients.)
> 
> If they don't like that negative impact, the only thing thing I can tell them is to
> use another e-mail provider, or to lobby yahoo.com to chainge their policies.
> If that happens to negatively impact yahoo.com, I can't say that I would be
> sorry.
> 

You are singing a different tune (at least in tone) than in your earlier posts.

_______________________________________________
ietf-822 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-822