IETF Logo Mail Archive

Re: DMARC stuff

"John R Levine" <johnl@taugh.com> Thu, 22 October 2015 17:33 UTC

Return-Path: <johnl@taugh.com>
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 1B7981B2A53 for <ietf@ietfa.amsl.com>; Thu, 22 Oct 2015 10:33:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.137
X-Spam-Level:
X-Spam-Status: No, score=-1.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, 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 1MWnRXzCmdr1 for <ietf@ietfa.amsl.com>; Thu, 22 Oct 2015 10:33:42 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 412EE1B2A50 for <ietf@ietf.org>; Thu, 22 Oct 2015 10:33:42 -0700 (PDT)
Received: (qmail 21468 invoked from network); 22 Oct 2015 17:33:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=53db.56291df6.k1510; bh=4/W4DCc60biozW1R5JzW279e1bK2uas0nq7v8kSHqJw=; b=qz4tVTSNbC5EUcn/nvtn3SgOzD9yPHzVFYfY3p0yfkCUCZiQMGIC/myGBgR4U6pjZpngabuEd2sJYeIfJ3UHU4k1li2TVUw36Emt0KUiYvM+eOZKA1vGUSW0xPhlib5BSBXuDVqLvMrvMhOtptRmlSK/bVcISfIBXeD7Kp8WXK5TFmPKC/cxxBvRi4+D7pyjm8mYviMyKB5TyLDhlqO4c4ZIkdCRv4+ru1+ydFRqXZjDJTMDqSJpm4ELOpzzFizu
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=53db.56291df6.k1510; bh=4/W4DCc60biozW1R5JzW279e1bK2uas0nq7v8kSHqJw=; b=FujiIAfmD2c1uBFrLDrhz1VBhCSEul96clpXqJnerwpZJ3XQ6uMXHEWPNbfBWpK7Yr/Fjn/fL4tv7yu0zQGDVn/fkB6pk6sPi3NzRvNFsfSZg5cR2EyBdor5EZeRU2eioKVPXCJYkmgLbBaon+5CqeBHvJdh06lakKOiq6R8M4aDfPK6K44lWwptuKZ4juk5qk7y+KVG2OWGLw6nnE4dW8Lz6pxvA7BMduhClyph01YcE7SelJa+hA8nPSowG/mK
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 22 Oct 2015 17:33:42 -0000
Date: Thu, 22 Oct 2015 13:33:39 -0400
Message-ID: <alpine.OSX.2.11.1510221328340.642@ary.local>
From: John R Levine <johnl@taugh.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: DMARC stuff
In-Reply-To: <32433.1445530303@sandelman.ca>
References: <20151022154248.4070.qmail@ary.lan> <32433.1445530303@sandelman.ca>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/f5AmHOmxw_rBNd6LIAs__pVa4Jk>
Cc: IETF general list <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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 22 Oct 2015 17:33:44 -0000

>    > Members of the DMARC group have submitted two drafts
>    > draft-andersen-arc-00 and draft-jones-arc-usage-00 which describe a
>    > mutation of DKIM intended to let mailing lists coexist with DMARC
>    > without having to do ugly hacks like rewriting the From: line.  I have
>    > reason to believe that several large mail systems intend to implement
>    > this reasonably soon.
>
> Can you at least summarize where the drafts are in the process, and if they
> require changes to senders, mailing lists, receivers, or all of the above?

ARC adds some new trace headers that provide a signed chain of custody. 
If you're already doing DKIM signing or verification, it should be 
straightforward to use upgraded DKIM libraries to apply them.  Receivers 
look at the ARC headers to decide when to accept a message despite DMARC 
failure.  As I said, big mail systems plan to do this.  There aren't any 
mailing list changes other than adding ARC headers which would be 
invisible to users.

> Are the proposals (which I guess are not yet adopted) complementary, or will
> a beauty contest be required?

The work is outside the IETF, no beauty contest.

> I think that ietf@ietf.org needs to know if we'll have a solution in time,
> or if the secretariat needs to be asked to deploy mailman 3 sooner.

I'd be pretty surprised if Gmail started publishing a DMARC policy before 
lists were able to deploy ARC.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

v2.23.0 | Report a Bug | By Email