Re: [ietf-smtp] Fwd: New Version Notification for draft-crocker-email-deliveredto-00.txt

Dave Crocker <dhc@dcrocker.net> Fri, 05 February 2021 21:53 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1500E3A0BFC for <ietf-smtp@ietfa.amsl.com>; Fri, 5 Feb 2021 13:53:43 -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 cF0YXa_3QBz0 for <ietf-smtp@ietfa.amsl.com>; Fri, 5 Feb 2021 13:53:41 -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 AAA9E3A0BFA for <ietf-smtp@ietf.org>; Fri, 5 Feb 2021 13:53:41 -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 95DB3362A96; Fri, 5 Feb 2021 21:53:40 +0000 (UTC)
Received: from nl-srv-smtpout1.hostinger.io (100-96-18-11.trex.outbound.svc.cluster.local [100.96.18.11]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 845C836318E; Fri, 5 Feb 2021 21:53:39 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from nl-srv-smtpout1.hostinger.io ([UNAVAILABLE]. [185.224.136.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.96.18.11 (trex/6.0.2); Fri, 05 Feb 2021 21:53:40 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Desert-Whistle: 06e11b9318100eb3_1612562020240_1545320115
X-MC-Loop-Signature: 1612562020240:2457985593
X-MC-Ingress-Time: 1612562020239
Received: from [192.168.0.109] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (Authenticated sender: dhc@dcrocker.net) by nl-srv-smtpout1.hostinger.io (smtp.hostinger.com) with ESMTPSA id 5CE2F22661D1; Fri, 5 Feb 2021 21:53:36 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1612562017; bh=TqDV5kgnwjg+9ojkG0BwT8qIdXvOfIIvG3mp6kooUYk=; h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To; b=EVsmaxh9hLJLQXO/OpENjsaFpF+12SeXfJbROXCgV/nWKUDYC/YUPjs/Qw66ORVEf lZgeyqINxOHlCsNOsBCpRBLgRccxxmRn0dykN1JCeapHiKv0TsDyV4B9BMCuckwgXE K1lpn7ZVQ57A6hYlU+uxLZ652rHHGkQmKaZKgoKvop8rEWRhzkpguwVM1thr6gVntI r+uTGnqWLLgfVMdnJyo/R82Eh3bRWx0lol6qY1pQA9zhGXlUdQpaRxaCZJKXlrU4Ut 4mbqwSKiwyq6CG4ywx+aOeef9WC5Q75r5U6GvI544isHOG5Z77YFwdm8sWD26tGXai yYfMoSuk/x5ig==
Reply-To: dcrocker@bbiw.net
To: Valdis Klētnieks <valdis.kletnieks@vt.edu>
Cc: ietf-smtp <ietf-smtp@ietf.org>
References: <161237978029.17564.1671203014287258223@ietfa.amsl.com> <ac72f2cc-7244-23d1-3615-a8f4e5f7388c@dcrocker.net> <468945c6-04f9-12c7-c49c-51badaf04ea2@tana.it> <33341.1612561465@turing-police>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <b0c79f55-b4e2-710c-b290-465c3210885c@dcrocker.net>
Date: Fri, 05 Feb 2021 13:53:34 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <33341.1612561465@turing-police>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/nJ0ioyZETVJp6JPdsaVq9bH_wdY>
Subject: Re: [ietf-smtp] Fwd: New Version Notification for draft-crocker-email-deliveredto-00.txt
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2021 21:53:43 -0000

On 2/5/2021 1:44 PM, Valdis Klētnieks wrote:
> On Fri, 05 Feb 2021 11:56:55 +0100, Alessandro Vesely said:
> 
>>      The Delivered-To: header field is added at the time of delivery, when
>>      responsibility for a message transitions from the Mail Handling
>>      (Transport) Service to an agent acting on behalf of the specified
>>      recipient address.
> 
> It's a plausible design that the agent doing final delivery accepts
> responsibility for delivery to multiple local mailboxes (I've often had things
> that ended up delivering to root@localhost and valdis@localhost with one
> invocation of the local delivery agent, for example).  Should the agent
> generate two Delivered-To: headers, or does it *actually* get generated
> appropriately for each copy (at a time later than when the agent accepted
> responsibility)?


The question for the specification is whether it makes clear what the 
specification calls for.  I think it does, but if readers aren't clear 
about it, it would be good to know what about it isn't clear enough.

A different question is how to implement the specification, so as to 
conform to the specification.

For storing a separate copy for each recipient, that seems straightforward.

For sharing a single copy of the message among multiple recipients, the 
answer probably is not straightforward...

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net