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

Alessandro Vesely <vesely@tana.it> Fri, 05 February 2021 19:34 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 5F1DE3A0F47 for <ietf-smtp@ietfa.amsl.com>; Fri, 5 Feb 2021 11:34:05 -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 5qHPgd13PFbd for <ietf-smtp@ietfa.amsl.com>; Fri, 5 Feb 2021 11:34:03 -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 1F15C3A0F46 for <ietf-smtp@ietf.org>; Fri, 5 Feb 2021 11:34:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612553638; bh=a14iDCcb+Xnap7TuSNQcvHGA1VpC0PbJ6SikZagrxGI=; l=1336; h=To:References:From:Date:In-Reply-To; b=Ae2V+g82tKK0xHhM+vRUt7UzaT3cybadB2DFsy+IqPK48LJ1Ua0HghmtoO09gPpM4 WqNSXHgnBe+hQ6eeLKrL0vD4/JqfttO0yT70+1StymmcPhpLfDcoe7MCUS+iXfzIE6 FfWRVWJ9l0q1sfBY1SG/Ez7S4RH48J7AMcHs2bw9iHVzqGYUO2WcYH4I5CNAQ
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.00000000601D9DA6.00007D67; Fri, 05 Feb 2021 20:33:58 +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> <468945c6-04f9-12c7-c49c-51badaf04ea2@tana.it> <01619e91-28c6-efaa-f6d1-da7b09fba615@dcrocker.net>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <b57de32f-3c81-9959-9806-6b7fcdda8263@tana.it>
Date: Fri, 05 Feb 2021 20:33:58 +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: <01619e91-28c6-efaa-f6d1-da7b09fba615@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/TOgHWJGuuz_b-f-zRXBX_ECJTDo>
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 19:34:06 -0000

On Fri 05/Feb/2021 15:53:16 +0100 Dave Crocker wrote:
> On 2/5/2021 2:56 AM, Alessandro Vesely wrote:
> 
>> 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?
> 
> I'd guess that has more to do with software implementation that document 
> specification, but if there's a change to this spec you have in mind, please 
> offer it.


Meanwhile, I had asked the same question to the developer.  Here's what he 
answered:

     Until mail client are dominantly Unicode, one still needs to make allowance
     for ASCII mail clients that might balk on seeing 8-bit mail headers, hence
     the headers Courier adds will have UTF-8 domains translated to their ACE
     equivalents.

     Courier should accept UTF-8 userids. Can't do anything about that, so
     they'll still show up as UTF-8 in headers. This will require the IMAP or
     the POP3 client to enable Unicode support, else they'll get that warning.

I don't think that that text should go in the I-D.  However, if you can extract 
a savvy principle from it, it may be worth to add it to the spec...


Best
Ale
--