Re: DMARC and yahoo

Theodore Ts'o <tytso@mit.edu> Tue, 15 April 2014 21:43 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 29A361A04A6 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 14:43:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level:
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ZPLftnYgWoCY for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 14:43:53 -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 4504C1A06A6 for <ietf@ietf.org>; Tue, 15 Apr 2014 14:43:53 -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 1WaB8v-0002mN-6M; Tue, 15 Apr 2014 21:43:49 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 86A1F580893; Tue, 15 Apr 2014 17:43:48 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397598228; bh=TAGd/pVl/LQJBtmkiNC1iVosl9V+opoHjFjjlD+l8e8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=cE+MNqId0hFuh57fvLT5Z6thzoYX7JGeVAVD4zCWTajFt5Jcor7coBl9JRmNVxaQx 7bruEjpNQuuu/L1ryw/MyPSAPJhueeYQK3gocvMBaiYB1wkbS7ZLk+ubbHeKN3TImw T5HhTMSxUnwMKGPZAVKkbxPA1Zg3glrsJdsG+8Do=
Date: Tue, 15 Apr 2014 17:43:48 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Doug Royer <douglasroyer@gmail.com>
Subject: Re: DMARC and yahoo
Message-ID: <20140415214348.GL4456@thunk.org>
References: <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> <534D5516.7060902@dcrocker.net> <534D98CC.9080400@gmail.com> <534D9C2C.8010606@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <534D9C2C.8010606@gmail.com>
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/7CWELVDfvEe-4aCiqWlOMAMhYK8
Cc: 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 21:43:55 -0000

On Tue, Apr 15, 2014 at 02:53:00PM -0600, Doug Royer wrote:
> Yahoo policy says you must have DKIM, SPF, or DMARC records. At what point
> could a large ISP start actually requiring these kinds of records for FREE
> email they accept and allow users to send?
> 
> Annoying, but it sounds reasonable to me for them to state a policy and
> enforce it.
> 
> If everyone had to wait until everyone upgraded, nothing would change.

The problem is with the alignment requirements of DMARC.  That can't
be easily fixed without breaking existing mailing list functionality.

Given that, it seems that the "From: username@yahoo.com.INVALID"
rewrite solution for mailing list, is the best solution, since it puts
the pain on yahoo.com users and people who want to communicate with
yahoo.com users.  If Yahoo wants to unilaterially allocate pain to the
rest of the Internet, then it shouldn't be surprised if people choose
a technical solution which transfer some of the pain back to Yahoo.

	  	   	 	       - Ted