Re: What I've been wondering about the DMARC problem

Theodore Ts'o <tytso@mit.edu> Tue, 15 April 2014 03:23 UTC

Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 489F11A0671 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:23:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.527
X-Spam-Level:
X-Spam-Status: No, score=0.527 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ejp6mqoJxD2c for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:23:19 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 2E3FC1A0663 for <ietf@ietf.org>; Mon, 14 Apr 2014 20:23:19 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WZtxq-0005VF-BJ; Tue, 15 Apr 2014 03:23:14 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 656F7580287; Mon, 14 Apr 2014 23:23:13 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397532193; bh=iY/LnGS3VnV3F23wsME6Mmlgs3xc8WCZ3cnnlncCxH8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=C8uASI3UkRNiyJ/s8/pysaOpDGtd+koL7IfJjFqR47BeromW857qXQdtsvl/dTMZJ unKdyUtw/jJw8sDqABblwmyp7ZhG+NbrW7+eyRdjOgKawFO9zL56hGcYBVRjK9Fu/b xEFnKhMtKlWhEUDAznYWwSMHeNxiqbU1eHHCwYBA=
Date: Mon, 14 Apr 2014 23:23:13 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: What I've been wondering about the DMARC problem
Message-ID: <20140415032313.GA3403@thunk.org>
References: <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534CA1AF.2040603@dougbarton.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <534CA1AF.2040603@dougbarton.us>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9xy4AhHtuMgZg0EVwsxkJC4ca8A
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 03:23:24 -0000

On Mon, Apr 14, 2014 at 08:04:15PM -0700, Doug Barton wrote:
> 
> Simple ... from Yahoo!'s perspective the breakage is negligible, not
> serious. Traditional e-mail traffic to and from traditional e-mail lists
> (like this one) is simply not large enough to lose sleep over. Keep in mind,
> Yahoo! knew what breakage was going to occur before they threw the switch,
> and they threw the switch anyway.
> 
> Again, I realize that it's hard for most IETF'ers to conceive of, but in
> this matter we are the ultimate anachronists.

The problem is that e-mail volume really is the wrong way to measure
"breakage".  After all, the vast majority of e-mail may be SPAM, but
that doesn't mean that those e-mail messages are the ones that any
users care about.

I've already had to send out message to my church's vestry (governing
board) explaining that people who are using Yahoo aren't going to be
able to send to the church mailing lists reliably, and that for now,
until I can get around to fixing the mailing list software (hint: not
during Holy Week), that their messages will be held for moderation
until someone can manually cut and paste it and send it on their
behalf.

I've also explained that if they care, they should consider
complaining to Yahoo and/or switching e-mail providers.

If enough people do the same, maybe Yahoo will reconsider.  If not, so
long most of my e-mail community switches mail providers (i.e.,
treating yahoo.com as damage, and routing around it), I may not care
all that much.

In the maintime, if someone has had the time to hack together some
patches to mailman to write the from field of yahoo.com users to be
yahoo.com.INVALID.  Please send them my way; I'll be most grateful.

		    	   	     	- Ted