IETF Logo Mail Archive

Re: [Emailcore] Delivered-To issues

Dave Crocker <dhc@dcrocker.net> Thu, 31 December 2020 22:45 UTC

Return-Path: <dhc@dcrocker.net>
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 EE3AB3A0CB3 for <emailcore@ietfa.amsl.com>; Thu, 31 Dec 2020 14:45:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=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=dcrocker.net
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 HEnL3ovvGN-H for <emailcore@ietfa.amsl.com>; Thu, 31 Dec 2020 14:45:37 -0800 (PST)
Received: from giraffe.ash.relay.mailchannels.net (giraffe.ash.relay.mailchannels.net [23.83.222.69]) (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 840293A0CAF for <emailcore@ietf.org>; Thu, 31 Dec 2020 14:45:35 -0800 (PST)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 3C837341A9B; Thu, 31 Dec 2020 22:45:32 +0000 (UTC)
Received: from nl-srv-smtpout2.hostinger.io (100-96-8-104.trex.outbound.svc.cluster.local [100.96.8.104]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id B7C80340F57; Thu, 31 Dec 2020 22:45:30 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from nl-srv-smtpout2.hostinger.io ([UNAVAILABLE]. [145.14.159.14]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.11); Thu, 31 Dec 2020 22:45:32 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Army-Befitting: 018eb02b7a9d94c2_1609454731941_1249058749
X-MC-Loop-Signature: 1609454731941:705256883
X-MC-Ingress-Time: 1609454731941
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net [24.130.62.181]) (Authenticated sender: dhc@dcrocker.net) by nl-srv-smtpout2.hostinger.io (smtp.hostinger.com) with ESMTPSA id 698E8333EFB7; Thu, 31 Dec 2020 22:45:26 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1609454729; bh=2ZH1TBsuq9XqxwTNJxoeGRYOZbcii4WMskz/2G//gJY=; h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To; b=mV7JCXcVk2Ngf3idj5Ovv4UgIpMD1uXHpm3nE7NZc/O4hyUMi9f6NeRj7qoPgcak8 73T/LZO+pKGXwdpe8G+A9e2eMDMZuWrWDJ6ggHYhkGQ/5wnul/iMEhpzrImva5K04D 32+/J1eh33QwjPHa+ZtKPgBwxOKeXmY7hW6XyvxMCmEYPMhXlJZn2PdPLVK+rdxnvL HCdiIqZIE5K9I+uDbWi6b1fNtbSCwFS2JSwWClr1xKjKZJILvaIpFrmLqxEzDuvdAk te07HeMRMfE6b/Tc2gQlkB73vwIQmbUUaWHC9MisVJIYTmOXGOoqeOBaZsbjLUh/5s xOBmt2tha7iKw==
Reply-To: dcrocker@bbiw.net
To: John Levine <johnl@taugh.com>, emailcore@ietf.org
Cc: dcrocker@bbiw.net
References: <20201231223339.D22303F108F2@ary.qy>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <5461cf6d-270a-cf39-12c0-9754acf90ed2@dcrocker.net>
Date: Thu, 31 Dec 2020 14:45:23 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20201231223339.D22303F108F2@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/uj8cl9EK7ysW8Yz6wypdT99ChTI>
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: Thu, 31 Dec 2020 22:45:39 -0000

On 12/31/2020 2:33 PM, John Levine wrote:
>> 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?

The language in Section 4.4, in the third bullet, might be claimed to 
imply this, but it doesn't actually say it.  And that bullet does not 
have a focus of defining the parameter's semantics.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email