Re: [Emailcore] Delivered-To issues

Dave Crocker <dhc@dcrocker.net> Fri, 01 January 2021 16:24 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 CA5EB3A005D for <emailcore@ietfa.amsl.com>; Fri, 1 Jan 2021 08:24:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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_H2=-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 6nMrTrxVDYgq for <emailcore@ietfa.amsl.com>; Fri, 1 Jan 2021 08:24:35 -0800 (PST)
Received: from cyan.elm.relay.mailchannels.net (cyan.elm.relay.mailchannels.net [23.83.212.47]) (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 462BB3A0045 for <emailcore@ietf.org>; Fri, 1 Jan 2021 08:24:34 -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 2D186701F82 for <emailcore@ietf.org>; Fri, 1 Jan 2021 16:24:34 +0000 (UTC)
Received: from nl-srv-smtpout3.hostinger.io (100-96-1-8.trex.outbound.svc.cluster.local [100.96.1.8]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 4419C701EF9 for <emailcore@ietf.org>; Fri, 1 Jan 2021 16:24:33 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from nl-srv-smtpout3.hostinger.io ([UNAVAILABLE]. [145.14.159.243]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.11); Fri, 01 Jan 2021 16:24:33 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Tart-Sponge: 3612c56e1491558c_1609518273816_980973486
X-MC-Loop-Signature: 1609518273816:3537922445
X-MC-Ingress-Time: 1609518273816
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-smtpout3.hostinger.io (smtp.hostinger.com) with ESMTPSA id 591B931C2C54 for <emailcore@ietf.org>; Fri, 1 Jan 2021 16:24:31 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1609518271; bh=dyWL3AxVxkNP36IyOZo8zLfZhI1pQqncXORRx2SC+Go=; h=Reply-To:Subject:From:To:References:Date:In-Reply-To; b=gjDPni3mhMM44QYUxLEN19Ed2HWoP5nle/YS05VpOZzErKaXhN3wkiYR04CsK/pXw pnuwGvIGKs9J9lKC66XzjBltAYR3lmr/5I6DLXRseM0yJzUGf6BlBNa9b7AYsWXK2u /IOLGL20wu8+JF+KvVDztg4+EZG0Gw0rTnDIjcpqSgzLPzQRC/8dmZL4bCcVC+jA3e 0MSRnuylC2HCMt7Of/Nx1P9ieFpiSsD5mmCJazD48bblpIP3IKcnjoIHlEi9Qg9YfL Pa90AnH0YYmt6TIukshnankTU/touKzOrNv14/yFBqj1gvF9k++GhQjDNVRb7hRDXM rWBQtGsercEeg==
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
To: emailcore@ietf.org
References: <4bc00e40-8a18-0c8c-bf1e-672e91da2330@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <def122c9-1eec-8828-6c17-1adb8d4c5ed9@dcrocker.net>
Date: Fri, 01 Jan 2021 08:24:29 -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: <4bc00e40-8a18-0c8c-bf1e-672e91da2330@dcrocker.net>
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/Rzq7PfxZZLFFug01CN50iwvn5-M>
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: Fri, 01 Jan 2021 16:24:37 -0000

On 12/31/2020 1:09 PM, Dave Crocker wrote:
> 3. ?


Drat.  Just started to throw some basic text into a draft and I've 
already run into an issue that might or might not creates some challenges.

Rather than pursue this in terms of fine-grained details, I'll ask you 
all to first consider what information we would like a recipient's MUA 
to have access to.  Then we can worry about how to engineer the details.

In the simple case, the RCPT TO contains an address and, indeed, the 
recipient's MUA resides at that address.  The message has gone through a 
single SMTP posting/delivering sequence.

Mailing lists (including Aliases) and other post-processing facilities, 
make things more interesting.  They create multiple posting/delivery 
sequences.  The final recipient address is not what the author generated 
in the initial RCPT TO field.

      Should the recipient's MUA have access to the /sequence/ of RCPT TO
      addresses used to get to them?

      Should they have only the final one?

      Should they have only the original one?

      Should they...?


Thoughts?


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net