Re: DMARC and yahoo

Doug Barton <dougb@dougbarton.us> Sun, 20 April 2014 21:23 UTC

Return-Path: <dougb@dougbarton.us>
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 05AAE1A0039 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 14:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.674
X-Spam-Level:
X-Spam-Status: No, score=-1.674 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 jzhIIR9UdOTb for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 14:23:50 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id DE5111A003B for <ietf@ietf.org>; Sun, 20 Apr 2014 14:23:50 -0700 (PDT)
Received: from [192.168.2.25] (unknown [99.17.30.3]) by dougbarton.us (Postfix) with ESMTPSA id 0056C22B20 for <ietf@ietf.org>; Sun, 20 Apr 2014 21:23:45 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1398029026; bh=O4QWH7cQSFeAc7auJ77OJlpK20Xb3YobUvI70tpAEFQ=; h=Date:From:To:Subject:References:In-Reply-To; b=VyTA760CFmBYg55I8Gf0P22LVqEzAGpDf8r+8dudBnZPG9+oX43Vi2rpn5Llj1/IK MMvSj6cUWrY5RI5pdYiRH91ruZFDfP9aQ4/J0F4p0yjKAl7R/798l5CNRY+E9qjT+v PN4oTugbGCSq3e83qC+UD8BHxZi7UikmSEgR+b2Q=
Message-ID: <53543ADA.8010204@dougbarton.us>
Date: Sun, 20 Apr 2014 14:23:38 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC and yahoo
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <20140416023813.GA21807@thunk.org> <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com> <4948F093F369F051CAF0B810@[192.168.1.128]>
In-Reply-To: <4948F093F369F051CAF0B810@[192.168.1.128]>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9Mb7M3k8PRjawoNcl58X-s6D8ww
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: Sun, 20 Apr 2014 21:23:55 -0000

On 04/20/2014 10:26 AM, John C Klensin wrote:
>
>
> --On Sunday, 20 April, 2014 12:52 -0400 Jeffrey Altman
> <jaltman@secure-endpoints.com> wrote:
>
>> ...
>> I took a different approach.  I left the bounce detection on
>> but switched all @yahoo.com accounts to digest mode.  Since
>> the mail now comes from the list instead of the @yahoo.com
>> sender there are no rejections.   Not a perfect solution but
>> it prevents harm to non-@yahoo.com list participants.
>
> IMO, this is quite elegant.  The Yahoo users continue to get the
> messages, you don't get cluttered by rejection-related
> complaints, and those Yahoo users who don't like the digest form
> can take it up with Yahoo or find other accounts to use.

The issue with @yahoo.com and DMARC is not the @yahoo.com users' ability 
to receive mail, it's their ability to send mail to the list with From: 
*@yahoo.com and have it be received by list subscribers who implement 
strict DMARC policies which honor Yahoo!'s p=reject.

It's not clear how setting the @yahoo.com users to digest mode helps 
this situation at all.

Doug