[ietf-smtp] How wrong is this EAI implementation

John R Levine <johnl@taugh.com> Sat, 20 June 2020 18:54 UTC

Return-Path: <johnl@taugh.com>
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 B1BE43A08FC for <ietf-smtp@ietfa.amsl.com>; Sat, 20 Jun 2020 11:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=TybvTZ0n; dkim=pass (1536-bit key) header.d=taugh.com header.b=iZXW/53j
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 Ejjlp_rfWTW0 for <ietf-smtp@ietfa.amsl.com>; Sat, 20 Jun 2020 11:54:19 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 971933A08FE for <ietf-smtp@ietf.org>; Sat, 20 Jun 2020 11:54:19 -0700 (PDT)
Received: (qmail 24542 invoked from network); 20 Jun 2020 18:54:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent; s=5fdc.5eee5b5a.k2006; i=johnl-iecc.com@submit.iecc.com; bh=YvaPMIXkuXWmyG7wG4BrkW2nlXYwaUoudgUXcB+9RqU=; b=TybvTZ0nrB65rid0/jLI59E+3ujb0T9zBkKi47vWRLGlVjQaOSmagTb5ZkmJ7uKD4lddkpQTjRtv29FHIsgAVRQ5h4hYqEdepr3ZnTNU3v6bDOkiY5SCyQqgXJDelZ+a7sgASR8ttcjXhnc3NmBh/L+tJmtkHXNrCxWFRJPTox/ZFtnTMo0dDsNK45vwKRL2mzz1h5iHY3iKWMQexCMSF3wfQU/zs5AoTiWe4Xl9RLGPmNq+/Gmc4WLA9QS+LBoF
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent; s=5fdc.5eee5b5a.k2006; olt=johnl-iecc.com@submit.iecc.com; bh=YvaPMIXkuXWmyG7wG4BrkW2nlXYwaUoudgUXcB+9RqU=; b=iZXW/53jQHX9Bme3z/Ta3ZQmOgQRvsSPMOcrzutY9MaYo/YSBZ2H8H5poKyZCkzAqC1q6vmhXoqlGOwQm3p8yd3yNwZfOFXu/Fcnl4BD4XLG793Pe+qI4U8G4BmLOcMlzp3FU5yXz0f55fistv9NGM2YBtsThSqcDlpaf1auB8Hgad4P4dU2t98nBjlFOroS5xXCElBs57GBKo8APyOWUMoKF8f9DfnBrcIR0+ALaWZYZg2qRhXAeSPtCJoAC5CD
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 20 Jun 2020 18:54:17 -0000
Date: 20 Jun 2020 14:54:17 -0400
Message-ID: <alpine.OSX.2.22.407.2006201429080.28792@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: ietf-smtp@ietf.org
User-Agent: Alpine 2.22 (OSX 407 2020-02-09)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-820800757-1592679258=:28792"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/X04jyZDS_mh2Jr0g3FQOhUHByK4>
Subject: [ietf-smtp] How wrong is this EAI implementation
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: Sat, 20 Jun 2020 18:54:22 -0000

I am poking at the widely used Roundcube web mail package.

One of my test addresses is 测试@电子邮件测试.中国

When I enter it into Roundcube as a username, it turns the domain into 
a-labels, 测试@xn--5nqx41au4nqohsp3axcg.xn--fiqs8s and uses that as the 
address in the From: line, and to authenticate to IMAP and 
submission.  I can understand where that came from, but it still seems 
wrong.

Addresses that I put on the To: line seem unmolested.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly