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

Alessandro Vesely <vesely@tana.it> Fri, 05 February 2021 10:57 UTC

Return-Path: <vesely@tana.it>
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 61FD43A0C40 for <ietf-smtp@ietfa.amsl.com>; Fri, 5 Feb 2021 02:57:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 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.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
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 FC3XkaRznPID for <ietf-smtp@ietfa.amsl.com>; Fri, 5 Feb 2021 02:57:00 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (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 48FD03A0C43 for <ietf-smtp@ietf.org>; Fri, 5 Feb 2021 02:57:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612522617; bh=y68anTTbyKPH5US47lCx7j91CJVTVm9xiIS1g85wsDk=; l=1808; h=To:References:From:Date:In-Reply-To; b=AoeVJgy3AhZdpNIglCcvul0TB7rm9TKUhboHifVV3b1i6DUgKpcUvJEnPcLBekF6o 6wgWG2wX20iDv5Cct8GaoVrttVG2R5nVXj0SwYvWEFN+Bcmhr61+VYtw+pGgIvdHqD voGArMHwSgarExVb1prCE5cz3z7sG32JdnF/UPTmMVVI43jIvD7NL4/TPR3yp
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC042.00000000601D2479.00003BA7; Fri, 05 Feb 2021 11:56:57 +0100
To: dcrocker@bbiw.net, ietf-smtp <ietf-smtp@ietf.org>
References: <161237978029.17564.1671203014287258223@ietfa.amsl.com> <ac72f2cc-7244-23d1-3615-a8f4e5f7388c@dcrocker.net>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <468945c6-04f9-12c7-c49c-51badaf04ea2@tana.it>
Date: Fri, 05 Feb 2021 11:56:55 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <ac72f2cc-7244-23d1-3615-a8f4e5f7388c@dcrocker.net>
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/djNFNOciF9fPQP35TqD4VdbBFw4>
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 10:57:02 -0000

Hi Dave,

On Thu 04/Feb/2021 22:46:06 +0100 Dave Crocker wrote:
> G'day SMTP folk,
> 
> This draft was prompted by discussion in the emailcore wg, but is outside the 
> scope of the wg charter.  So the spec is being pursued as AD-sponsored.


A few points:

1)  In the sentence:

    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.

(Please substitute /Mail Handling/Message Handling/, so that it matches RFC 
5598.  Perhaps substituting /Transport/SMTP/ might improve readability.)

That sentence implies there is no Delivered-To: if the message is copied 
locally without going through MHS.  For example, some MDAs accept either email 
addresses (local or remote) or local mailbox paths to deliver a copy.  If one 
specifies delivery by means of local paths, no further Delivered-To: is added 
(and neither could be, since the agent doesn't know the address in that case). 
  Is that worth noting?

BTW, you don't use the term Message Delivery Agent (MDA).  Is it by purpose?


2) ABNF

    "Delivered-To:" FWS Mailbox CRLF

    Note:    The field records only a single address, for one recipient.

Would it be worth to note that Mailbox (capital M) comes from [SMTP], not 
[Mail-Fmt]?


3) IDNs:

When I write a message to user@foà.it (fake user, real domain) the MDA writes
Delivered-To: user@xn--fo-kia.it.  I see no reason for doing so.  The message 
is SMTPUTF8 anyway because of the To: user@foà.it header field, which is 
maintained.  Are there reasons to mangle the domain name?


> The SMTP mailing list is cited in the draft as the discussion venue.


Didn't find that citation.


Best
Ale
--