[170799] in North American Network Operators' Group
Re: Yahoo DMARC breakage
daemon@ATHENA.MIT.EDU (Jim Popovitch)
Wed Apr 9 17:35:55 2014
In-Reply-To: <CAP-guGXZSvDiNnKwgMPac8FY=UM8xGMXs85CpoOuJgtfzJwcCg@mail.gmail.com>
Date: Wed, 9 Apr 2014 17:35:26 -0400
From: Jim Popovitch <jimpop@gmail.com>
To: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Wed, Apr 9, 2014 at 5:15 PM, William Herrin <bill@herrin.us> wrote:
> On Wed, Apr 9, 2014 at 4:05 PM, John Levine <johnl@iecc.com> wrote:
>> I'd say it's pretty badly broken if Yahoo intends for their web mail
>> to continue to be a general purpose mail system for consumers. If
>> they want to make it something else, that's certainly their right, but
>> it would have been nice if they'd given us some advance warning so we
>> could take the yahoo.com addresses off our lists.
>
> Meh. This just means list software will have to rewrite the From
> header to "From: John Levine <nanog@nanog.org>" and rely on the
> Reply-To header for anybody who wants to send a message back to the
> originator.
Or perhaps DMARC can go back to it's original goal.
Go here: https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/
Notice the early versions of the spec contained the word
"transactional", notice the current version has it removed. Also
notice that one of the authors is from Yahoo!.
> Maybe this is a good thing - we can stop getting all the "sorry I'm
> out of the office" emails when posting to a list.
The OoO problem is a Client/MUA problem. Most (other than Lotus
Notes, and some older copies of Outlook) properly tag OoO emails with
well-defined headers (RFC 3834).
-Jim P.
