Re: [Emailcore] Delivered-To issues

John R Levine <johnl@taugh.com> Sat, 02 January 2021 01:25 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: emailcore@ietfa.amsl.com
Delivered-To: emailcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44E733A0418 for <emailcore@ietfa.amsl.com>; Fri, 1 Jan 2021 17:25:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=qhuhbD18; dkim=pass (2048-bit key) header.d=taugh.com header.b=lE/a2Om6
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 JUK8hKL6OW3z for <emailcore@ietfa.amsl.com>; Fri, 1 Jan 2021 17:25:14 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 194BB3A040B for <emailcore@ietf.org>; Fri, 1 Jan 2021 17:25:13 -0800 (PST)
Received: (qmail 12983 invoked from network); 2 Jan 2021 01:25:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=32b4.5fefcb78.k2101; i=johnl-iecc.com@submit.iecc.com; bh=g+/CZi6z6P2nYJWRKfMt7APdY2oGVHoYyDE3U3t1po8=; b=qhuhbD18g8a4HwAUFOEXcc4EwIuJgQnH059VdXMtM7qMA/Sf1bZjIyu3r9RuALaYVHwbhXDXflX7Z+0q6LnWWcJSaPZKcvlxfHJ4OcS3WCpUogYIjRxbv+5oDfjS/gestV9ONKaUJDcL9H0iH3GiZr01OIZxdMpxMwxapyMRuft5jV9urz4q+iBsalsmW7kQPLLmp3dtfHYOeHtthD/E4h7Za45DmPzrG3/rrEfBN4KDAsCrCZyd3NOEVHl1ieo5+cLlwVKJuiZX/tvkAY+IXjChvWouXeShf7dQmESgiirfQ48kulWR0uFNGjRSoN/QPCVXYz8CpDJS1HVH+WD80A==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=32b4.5fefcb78.k2101; olt=johnl-iecc.com@submit.iecc.com; bh=g+/CZi6z6P2nYJWRKfMt7APdY2oGVHoYyDE3U3t1po8=; b=lE/a2Om66d/EKZgBFNihN6R38Qc9o3N0xkMlBztHfqV4ilB9DpQBd39riCbgu1PcA+dTgy/IrmVUn1+/94Skjg5NFRc71IMvrxQlK5rKHUC8wdY+emFE/Vwi3Eb/dyQCLkxP7anPw0hl8Py9m07lQ6MIKruupQ671RNPQgJTC5rGZy+3BhPf8niDZZxleWH/G1T0xp9xuMEwu7kkPJB/Ri/KwpD2pChQ6sSSZo5em2QhNVN5t2M4veaVrQx9FVLuWItp3ALJbuU3qQ/3+ZMMNIxSdL3PcxkkwRRG/0sRQwlNM1VGWN44i0N2TPeftpbXwqcOVB9+dm7gROiWfGJbBA==
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 02 Jan 2021 01:25:12 -0000
Date: Fri, 01 Jan 2021 20:25:11 -0500
Message-ID: <f7f8232d-618f-672-ea7f-23e3fd9f6732@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Dave Crocker <dcrocker@bbiw.net>, emailcore@ietf.org
In-Reply-To: <5461cf6d-270a-cf39-12c0-9754acf90ed2@dcrocker.net>
References: <20201231223339.D22303F108F2@ary.qy> <5461cf6d-270a-cf39-12c0-9754acf90ed2@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/ShL7r9Sy5oE0hQ0tD2BL5BJSEiw>
Subject: Re: [Emailcore] Delivered-To issues
X-BeenThere: emailcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EMAILCORE proposed working group list <emailcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emailcore>, <mailto:emailcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emailcore/>
List-Post: <mailto:emailcore@ietf.org>
List-Help: <mailto:emailcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emailcore>, <mailto:emailcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jan 2021 01:25:16 -0000

>>> 1.  Why a separate header field, rather than Received's FOR clause?
>> What jck said, the mailbox into which a message is delivered often has
>> a different name from what was in the RCPT TO.  That's particularly
>> likely on systems that handle mail for multiple domains.
>
> with apologies to all, for my reading comprehension, limitations, but would 
> someone point to the place in RFC 5321 where the semantics of the FOR clause 
> are explained, and especially in terms of it's coming from a RCPT TO?

I don't think it does.  Section 4.4 says it contains one path even if 
there are multiple RCPT commands, 7.2 says sort of indirectly not to put 
blind recipient addresses into the received header, 7.6 reiterates the 
blind recipient stuff.

On the other hand I think it is clear from context that the FOR clause is 
supposed to contain a RCPT TO argument, with considerable ambigiuity which 
one to use if there were several recipients, and whether to include it at 
all.

The stuff in 7.2 and 7.6 seems to be saying to look at the message header 
and only include the FOR if it matches one of the header recipients, but 
ugh.

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