Re: Will mailing lists survive DMARC?

Dave Crocker <dhc@dcrocker.net> Tue, 29 April 2014 13:41 UTC

Return-Path: <dhc@dcrocker.net>
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 01F081A08DC for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 6UC_wA2V2LHc for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:41:05 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 010871A08D0 for <ietf@ietf.org>; Tue, 29 Apr 2014 06:41:05 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3TDf0aC031407 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 29 Apr 2014 06:41:04 -0700
Message-ID: <535FABE9.5060103@dcrocker.net>
Date: Tue, 29 Apr 2014 06:40:57 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>, ietf@ietf.org
Subject: Re: Will mailing lists survive DMARC?
References: <20140429124528.GA1324@mx1.yitter.info> <alpine.DEB.2.02.1404291502320.29282@uplift.swm.pp.se> <535FA739.3060608@dcrocker.net> <alpine.DEB.2.02.1404291524500.29282@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1404291524500.29282@uplift.swm.pp.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 29 Apr 2014 06:41:04 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LBfe_NfSnIICDmc8-ggDQ1xhO0U
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 29 Apr 2014 13:41:06 -0000

On 4/29/2014 6:29 AM, Mikael Abrahamsson wrote:
>
> So... just because this is a hard problem to solve doesn't mean it's a
> good idea to just gloss over it and say "screw it" for mailing lists.


A counter-argument is the classic "Don't let perfect be the enemy of 
good".  DMARC works well for a very popular -- albeit very constrained 
-- scenario.

For any mechanism, there is always the possibility that someone will 
apply it for scenarios beyond what was originally envisioned.  Often 
that is a large benefit.  Often is not always.

The distinctive issue now is that that extension is being done by very 
large players.  The phrase "Too big to ignore" has been rattling around 
in my brain for the last few weeks...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net