Re: [IETF] DMARC methods in mailman

Viktor Dukhovni <> Sat, 24 December 2016 18:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B6144129641 for <>; Sat, 24 Dec 2016 10:45:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GLrNARWBdZEH for <>; Sat, 24 Dec 2016 10:45:15 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 60F6512962F for <>; Sat, 24 Dec 2016 10:45:15 -0800 (PST)
Received: from [IPv6:2604:2000:1382:81a2:300e:e520:130e:a1c0] (unknown [IPv6:2604:2000:1382:81a2:300e:e520:130e:a1c0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 19258284B55 for <>; Sat, 24 Dec 2016 18:45:14 +0000 (UTC) (envelope-from
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [IETF] DMARC methods in mailman
From: Viktor Dukhovni <>
In-Reply-To: <>
Date: Sat, 24 Dec 2016 13:45:12 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <>
References: <001801d25d6a$4c267130$e4735390$> <20161223174224.9677.qmail@ary.lan> <>
To: IETF general list <>
X-Mailer: Apple Mail (2.3259)
Archived-At: <>
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <>
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 24 Dec 2016 18:45:16 -0000

> On Dec 24, 2016, at 1:25 AM, Randy Bush <> wrote:
> "If you want to participate in IETF mailing lists, you should be able to
> receive messages from and send messages to the IETF which follow
> Internet standards."

Sure, but, ultimately, what's the goal of this discussion?  Presumably
some workable configuration of the list managers that serves the needs
of IETF list members (possibly with some adjustment of how participants
interact with the lists).

So, if this discussion is to get anywhere, there needs to emerge a
consensus on the usability requirements for the lists.  At least
the following need to be understood:

   1. Must WG lists add [WG] subject tags?  Or can this be left to
      subscriber etiquette?

   2. Are message footers are a requirement?

   3. Is modification of the "From" header acceptable?

Discussion of whether to exclude subscribers from domains with
DMARC policy are not necessary if some acceptable combination
of the choices in 1, 2, 3 (or perhaps other options I left out)
works with DMARC and retains list usability.

As I mentioned before, for me, the most usable option is avoiding
message modification of any kind, which leaves the origin DKIM
signature valid.  I've not seen anyone comment on whether that's
workable for IETF WG lists (it works well enough for *this* list).