Re: Problem with the draft-all aliases

Viktor Dukhovni <> Tue, 03 January 2017 20:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 52D4A1296FB for <>; Tue, 3 Jan 2017 12:54:53 -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 j0UPF-eU5cBP for <>; Tue, 3 Jan 2017 12:54:51 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B102A1296FA for <>; Tue, 3 Jan 2017 12:54:51 -0800 (PST)
Received: from [] ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 76FB8282D54 for <>; Tue, 3 Jan 2017 20:54:50 +0000 (UTC) (envelope-from
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Problem with the draft-all aliases
From: Viktor Dukhovni <>
In-Reply-To: <095301d26601$72b1c8a0$581559e0$>
Date: Tue, 3 Jan 2017 15:54:49 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <095301d26601$72b1c8a0$581559e0$>
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: Tue, 03 Jan 2017 20:54:53 -0000

> On Jan 3, 2017, at 3:39 PM, Christian Huitema <> wrote:
> I just copied the review directly to the authors' individual addresses, and
> they received it fine. But obviously, something is wrong in the IETF's
> guidance to reviewers, or in the implementation of these expansion lists.
> The simple "exploder" function just does not work if the sender is left to
> the original "from" address. That exploder function is not compatible with
> SPF, or presumably with DMARC. Who would be a good contact to discuss
> improvements?

IIRC Glen from AMSL reads this list, in which case the message has already
reached the right ears.  As for possible remediation, if the lists are
implemented as local aliases(5) in the Postfix server, then assigning
an "owner-" alias to the list is sufficient to avoid trouble with SPF and simple
forwarding should not break DKIM or DMARC.

The aliases(5) file (or its database representation) would then contain
something along the lines of:

	document.all: author1@a.example, author2@b.example