Re: IETF Mailing Lists and DMARC

"John Levine" <johnl@taugh.com> Wed, 02 November 2016 17:43 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 9AE4E1296FD for <ietf@ietfa.amsl.com>; Wed, 2 Nov 2016 10:43:58 -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 7lww7r-Ylos0 for <ietf@ietfa.amsl.com>; Wed, 2 Nov 2016 10:43:55 -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 8D1DF12956A for <ietf@ietf.org>; Wed, 2 Nov 2016 10:43:55 -0700 (PDT)
Received: (qmail 21339 invoked from network); 2 Nov 2016 17:43:55 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 2 Nov 2016 17:43:55 -0000
Date: Wed, 02 Nov 2016 17:43:42 -0000
Message-ID: <20161102174342.67143.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF Mailing Lists and DMARC
In-Reply-To: <CAPt1N1=_jvrNbhxDyWXpJszUtqRZEEouRibwgWD1aY5wfhsX_Q@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/jf3WZ7swsNQVvpULT9tjFuqO8Lw>
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 17:43:58 -0000

In article <CAPt1N1=_jvrNbhxDyWXpJszUtqRZEEouRibwgWD1aY5wfhsX_Q@mail.gmail.com> you write:
>There's a pretty clear ops problem here that could be solved by simply
>detecting addresses with DMARC and rewriting the From: headers on
>those messages.   This would eliminate all problems immediately.

Assuming you mean replacing the actual author's address with the
list's address, that has the cost of breaking the way mailing lists
have worked for 30 years, and in particular making replies to the
author unworkable.  Many people would strenously disagree that this
"eliminates all problems", but merely replaces one problem with
another.

There are other workarounds with different costs and benefits, e.g.,
the one I use that rewrites DMARC'ed addresses into local temporary
forwarding addresses, in my case in the trendy dmarc.fail domain.
That lets people keep using lists the way they have but requires more
mail system hackery than most list managers are able or willing to do.

Again, this has been discussed at great length here and on many
mail-related lists.  Please see the archives.

R's,
John