IETF Logo Mail Archive

Re: Will mailing lists survive DMARC?

Dave Crocker <dhc@dcrocker.net> Tue, 29 April 2014 13:21 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 2C5701A08E0 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:21:24 -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 wW1VX-7aTCOv for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:21:17 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 400581A08DE for <ietf@ietf.org>; Tue, 29 Apr 2014 06:21:17 -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 s3TDLAuM031008 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 29 Apr 2014 06:21:14 -0700
Message-ID: <535FA739.3060608@dcrocker.net>
Date: Tue, 29 Apr 2014 06:20: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>, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: Will mailing lists survive DMARC?
References: <20140429124528.GA1324@mx1.yitter.info> <alpine.DEB.2.02.1404291502320.29282@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1404291502320.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:21:14 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/st3y5ZM5K72cEZvRUeo79i47Pm8
Cc: ietf@ietf.org
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:21:24 -0000

On 4/29/2014 6:03 AM, Mikael Abrahamsson wrote:
> I quickly went through
> https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/?include_text=1
> which I guess is the draft we're discussing? As far as I can tell, it
> doesn't "inform" about the problem DMARC causes in conjunction with
> quite prevalent mailing list functionality.


Well, it does, but not in the most pedagogical fashion one might wish 
for.  "Obscure" wouldn't be an inappropriate characterization...

    Appendix C.  DMARC XML Schema
    ...
    Descriptions of the PolicyOverrideTypes:
    ...
    mailing_list:  Local heuristics determined that the message arrived
       via a mailing list, and thus authentication of the original
       message was not expected to succeed.

The draft BCP is another opportunity to clarify such issues, and already 
has some text:

      http://tools.ietf.org/html/draft-crocker-dmarc-bcp-03

      11. DMARC Commentary -- What were they thinking of...?
      ...
      Why doesn't DMARC solve its problem with mailing lists/gatewats?

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email