I'd suggest reading up on DMARC. The goal of which is to allow a domain owner to prevent use of their domain name by bad guys. In this case, Yahoo wants to keep non-Yahoo servers from sending mail with a Yahoo 822 From header. Mailing lists get caught in the crossfire, but can be fixed pretty easily. (There's a whole separate argument over whether or not this is a good thing. I take the pragmatic view that regardless of opinion, it's out there and has to be dealt with, so that's what I focus on.)
https://dmarc.org/ is a good place to start. Cheers, Al Iverson -- Al Iverson www.aliverson.com (312)725-0130 On Wed, Jun 15, 2016 at 9:12 AM, Geoff Mulligan <ge...@proto6.com> wrote: > I guess what I'm trying to understand is why anyone would base their > acceptance or rejection on the 822 From: header. It seems that this causes > mailing list managers to have to jump through hoops to rewrite the From: > header in strange ways. > > Geoff > > > > On 06/15/2016 06:16 AM, Brandon Long via mailop wrote: > > So, we've been doing dmarc rejects for many years, for Yahoo.com since they > went p=reject two years ago. > > We may sometimes override the rejection, but no one should rely on that. > > I don't know of anything that has changed recently about this. > > Forwarding doesn't break with this unless you modify the mail or the > original message wasn't dkim authenticated. We've seen some recent examples > of banks going p=quarantine while only doing spf auth, which obviously > doesn't survive forwarding. > > Brandon > > > On Jun 15, 2016 1:57 AM, "Jeffry Dwight" <jeffry.dwi...@greyware.com> wrote: >> >> Sorry for the bad example. We don't use spaces when sending email out, >> although >> as Jon Postel would have approved, we accept them for incoming mail. There >> are a >> lot of broken MTAs out there. >> >> Jeffry >> >> --- Original Message --- >> From: <ml+mai...@esmtp.org> >> To: mailop@mailop.org >> CC: >> Date: Tue, 14 Jun 2016 20:23:36 -0700 >> Subject: Re: [mailop] change at gmail??? >> >> > On Tue, Jun 14, 2016, Jeffry Dwight wrote: >> >> > MAIL FROM: >> > RCPT TO: >> >> RFC 5321 SMTP October 2008 >> .. >> Since it has been a common source of errors, it is worth noting that >> spaces are not permitted on either side of the colon following FROM >> in the MAIL command or TO in the RCPT command. The syntax is exactly >> as given above. >> >> >> _______________________________________________ >> mailop mailing list >> mailop@mailop.org >> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >> >> >> >> _______________________________________________ >> mailop mailing list >> mailop@mailop.org >> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > > > -- > > -- > Â Geoff Mulligan > Â Chairman LoRa Alliance > Â Founder IPSO Alliance > Â Former White House Presidential Innovation Fellow > > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
