By their statement it's obvious that yahoo doesn't care about what they broke. It's unfortunate that email has become so centralized that one entity can cause so much 'trouble'. Maybe it's a good opportunity to encourage the affected mailing list subscribers to use their own domains for email, and host it themselves if possible.
-Laszlo On Apr 14, 2014, at 5:05 PM, Miles Fidelman <mfidel...@meetinghouse.net> wrote: > Isn't it the other way around? They don't want their users to be able to > send to mailing lists. They receive traffic from the lists just fine. Their > policy considers only effects mail originating from their users. Yahoo > subscribers can receive messages form nanog just fine, but they can't send to > it. > > Miles > > Laszlo Hanyecz wrote: >> I don't see what the big deal is here. They don't want your messages and >> they made that clear. Their policy considers these messages spam. If you >> really want to get your mailing list messages through, then you need to >> evade their filters just like every other spammer has to. >> >> -Laszlo >> >> >> On Apr 14, 2014, at 4:32 PM, Miles Fidelman <mfidel...@meetinghouse.net> >> wrote: >> >>> Well... how about this, from Yahoo's own posting: >>> We know there are about 30,000 affected email sending services, but we also >>> know that the change needed to support our new DMARC policy is important >>> and not terribly difficult to implement. >>> >>> To me - this sure looks, smells, and quacks like a denial-of-service attack >>> against a system I operate, and the subscriber to the lists that I support >>> -- somewhat akin to exploding a bomb in a public square, and then taking >>> credit for it. >>> >>> Miles Fidelman >>> >>> -- >>> In theory, there is no difference between theory and practice. >>> In practice, there is. .... Yogi Berra >>> >>> > > > -- > In theory, there is no difference between theory and practice. > In practice, there is. .... Yogi Berra > >
