IETF Logo Mail Archive

Re: IETF Mailing Lists and DMARC

"John Levine" <johnl@taugh.com> Wed, 02 November 2016 16:56 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BC3012945B for <ietf@ietfa.amsl.com>; Wed, 2 Nov 2016 09:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 23ExGFJ9Dgc0 for <ietf@ietfa.amsl.com>; Wed, 2 Nov 2016 09:56:13 -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-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09CEC12943F for <ietf@ietf.org>; Wed, 2 Nov 2016 09:56:12 -0700 (PDT)
Received: (qmail 8168 invoked from network); 2 Nov 2016 16:56:13 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 2 Nov 2016 16:56:13 -0000
Date: Wed, 02 Nov 2016 16:56:00 -0000
Message-ID: <20161102165600.67029.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF Mailing Lists and DMARC
In-Reply-To: <CAPt1N1k1wg9mbN-guuarFP0NvX7v-suOY-bP=TDEOCVhK-epmg@mail.gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C90_ucKTYjNXM7zwfjKj0_zZI-Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 02 Nov 2016 16:56:14 -0000

In article <CAPt1N1k1wg9mbN-guuarFP0NvX7v-suOY-bP=TDEOCVhK-epmg@mail.gmail.com> you write:
>And yet it is still happening, despite there being a great deal of
>discussion in the archives...   :/

Yes, because at this point, all of the solutions are worse than the
problem.  See this page for a roundup of DMARC mitigations:

http://wiki.asrg.sp.am/wiki/Mitigating_DMARC_damage_to_third_party_mail

The work on ARC is coming along fairly fast.  There was a second
compatibility event a couple of weeks ago among various
implementations, and people tell me there should be usable libraries
around the end of the year.  Once there's an ARC addon for Mailman and
we use that, the DMARC damage should drop considerably, without us
having to change the way we use our lists.

R's,
John

v2.23.0 | Report a Bug | By Email