From arnt@gulbrandsen.priv.no Tue Sep 10 10:16:37 2013 Return-Path: X-Original-To: ima@ietfa.amsl.com Delivered-To: ima@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B41DE21F91C9 for ; Tue, 10 Sep 2013 10:16:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F9s1Ssvz1x1e for ; Tue, 10 Sep 2013 10:16:37 -0700 (PDT) Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C79721F91B7 for ; Tue, 10 Sep 2013 10:16:36 -0700 (PDT) Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 58C24FA013B; Tue, 10 Sep 2013 17:16:35 +0000 (UTC) Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.4) with esmtpsa id 1378833394-6490-6488/11/10; Tue, 10 Sep 2013 17:16:34 +0000 Date: Tue, 10 Sep 2013 19:17:50 +0200 From: Arnt Gulbrandsen To: ima@ietf.org Message-Id: <20130910171743.GA26026@gulbrandsen.priv.no> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [EAI] Partly internationalised mail X-BeenThere: ima@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "EAI \(Email Address Internationalization\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Sep 2013 17:16:37 -0000 Hi, consider the following field: To: =C6 <=E6@example.com>, =C5 That is indubitably a valid EAI field. But then consider: To: =C6 <=E6@example.com>, =3D?q?iso-8859-1?FF=3D? I can't remember the 2047 rules, despite having implemented them twice. But you get the point. That is, as far as I can see, valid. Perhaps somewhat surprising. I did not expect that my code would use both UTF-8-EAI-ish syntax and 2047 syntax in the same field. But it seems valid, and the code is the most straightforward implementation was the simplest design. Arnt From klensin@jck.com Tue Sep 10 11:02:30 2013 Return-Path: X-Original-To: ima@ietfa.amsl.com Delivered-To: ima@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88E0F21E811D for ; Tue, 10 Sep 2013 11:02:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bB38Ux12QB2i for ; Tue, 10 Sep 2013 11:02:23 -0700 (PDT) Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id BFACC21E8127 for ; Tue, 10 Sep 2013 11:02:23 -0700 (PDT) Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from ) id 1VJSGb-000Lvk-Pw; Tue, 10 Sep 2013 14:02:21 -0400 Date: Tue, 10 Sep 2013 14:02:16 -0400 From: John C Klensin To: Arnt Gulbrandsen , ima@ietf.org Message-ID: In-Reply-To: <20130910171743.GA26026@gulbrandsen.priv.no> References: <20130910171743.GA26026@gulbrandsen.priv.no> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Re: [EAI] Partly internationalised mail X-BeenThere: ima@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "EAI \(Email Address Internationalization\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Sep 2013 18:02:30 -0000 --On Tuesday, September 10, 2013 19:17 +0200 Arnt Gulbrandsen wrote: > Hi, >=20 > consider the following field: >=20 > To: =C3=86 <=C3=A6@example.com>, =C3=85 >=20 > That is indubitably a valid EAI field. But then consider: >=20 > To: =C3=86 <=C3=A6@example.com>, =3D?q?iso-8859-1?FF=3D? = >=20 > I can't remember the 2047 rules, despite having implemented > them twice. But you get the point. That is, as far as I can > see, valid. Valid but in bad taste. EAI discourages any use of encoded words in headers in favor of decoding them into UTF-8. I can't remember if it actually says "SHOULD NOT" do the above, but, again, the intent was to discourage and get rid of that usage (and, in the process, of non-Unicode creatures like 8859-1). > Perhaps somewhat surprising. I did not expect that my code > would use both UTF-8-EAI-ish syntax and 2047 syntax in the > same field. But it seems valid, and the code is the most > straightforward implementation was the simplest design. It is hard or impossible to prohibit encoded words entirely because one can't compel the EAI client MUA to have decoders for every charset that might appear in such a thing (especially From: header fields and To: header fields generated by replies. Suppose you receive something containing=20 From: =3D?q?johns-made-up-charset?FF00FF=3D? The sender would clearly have been bad by not registering it with IANA and you have no hope of decoding it into Unicode. You could give it a high "sender-is-probably-an-idiot" score and, if you believe that most spammers are idiots and that most idiots are also spammers, maybe a high "probably-spam" score. But you probably aren't going to reject it so, when the user tries to reply... =20 >From a protocol point of view, that is just another reason to encourage on-the-wire use of nothing but UTF-8 these days and for discouraging use of encoded words, even encoded UTF-8. But... john From yaojk@cnnic.cn Wed Sep 11 00:56:10 2013 Return-Path: X-Original-To: ima@ietfa.amsl.com Delivered-To: ima@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B3DF21F85EE for ; Wed, 11 Sep 2013 00:56:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.998 X-Spam-Level: X-Spam-Status: No, score=-99.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XZoLSKFO5CqF for ; Wed, 11 Sep 2013 00:56:05 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id EB1B721E8096 for ; Wed, 11 Sep 2013 00:55:55 -0700 (PDT) X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn Received: from unknown127.0.0.1 (HELO healthyao-think) (127.0.0.1) by 127.0.0.1 with SMTP; Wed, 11 Sep 2013 15:55:39 +0800 Date: Wed, 11 Sep 2013 16:03:13 +0800 From: "Jiankang Yao" To: "Arnt Gulbrandsen" , ima References: <20130910171743.GA26026@gulbrandsen.priv.no> X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7.0.1.92[cn] Mime-Version: 1.0 Message-ID: <201309111603003324203@cnnic.cn> Content-Type: multipart/alternative; boundary="----=_001_NextPart508855211432_=----" Subject: Re: [EAI] Partly internationalised mail X-BeenThere: ima@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: yaojk List-Id: "EAI \(Email Address Internationalization\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Sep 2013 07:56:10 -0000 This is a multi-part message in MIME format. ------=_001_NextPart508855211432_=---- Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SSBoYXZlIHNlZW4gc29tZSBzaW1pbGFyIGltcGxlbWVuYXRpb24gZXhhbXBsZSBpbiB0aGUgY3Vy cmVudCBpbXBsZW1lbnRhdGlvbi4NCg0KVG86IMOGIDzDpkBleGFtcGxlLmNvbT4sID0/cT9pc28t ODg1OS0xP0ZGPT8gPGZmQGV4YW1wbGUuY29tPg0KDQoNCg0KDQpKaWFua2FuZyBZYW8NCg0KRnJv bTogQXJudCBHdWxicmFuZHNlbg0KRGF0ZTogMjAxMy0wOS0xMSAwMToxNw0KVG86IGltYQ0KU3Vi amVjdDogW0VBSV0gUGFydGx5IGludGVybmF0aW9uYWxpc2VkIG1haWwNCkhpLA0KDQpjb25zaWRl ciB0aGUgZm9sbG93aW5nIGZpZWxkOg0KDQpUbzogw4YgPMOmQGV4YW1wbGUuY29tPiwgw4UgPGZm QGV4YW1wbGUuY29tPg0KDQpUaGF0IGlzIGluZHViaXRhYmx5IGEgdmFsaWQgRUFJIGZpZWxkLiBC dXQgdGhlbiBjb25zaWRlcjoNCg0KVG86IMOGIDzDpkBleGFtcGxlLmNvbT4sID0/cT9pc28tODg1 OS0xP0ZGPT8gPGZmQGV4YW1wbGUuY29tPg0KDQpJIGNhbid0IHJlbWVtYmVyIHRoZSAyMDQ3IHJ1 bGVzLCBkZXNwaXRlIGhhdmluZyBpbXBsZW1lbnRlZCB0aGVtDQp0d2ljZS4gQnV0IHlvdSBnZXQg dGhlIHBvaW50LiBUaGF0IGlzLCBhcyBmYXIgYXMgSSBjYW4gc2VlLCB2YWxpZC4NCg0KUGVyaGFw cyBzb21ld2hhdCBzdXJwcmlzaW5nLiBJIGRpZCBub3QgZXhwZWN0IHRoYXQgbXkgY29kZSB3b3Vs ZCB1c2UNCmJvdGggVVRGLTgtRUFJLWlzaCBzeW50YXggYW5kIDIwNDcgc3ludGF4IGluIHRoZSBz YW1lIGZpZWxkLiBCdXQgaXQNCnNlZW1zIHZhbGlkLCBhbmQgdGhlIGNvZGUgaXMgdGhlIG1vc3Qg c3RyYWlnaHRmb3J3YXJkIGltcGxlbWVudGF0aW9uDQp3YXMgdGhlIHNpbXBsZXN0IGRlc2lnbi4N Cg0KQXJudA0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N CklNQSBtYWlsaW5nIGxpc3QNCklNQUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp bG1hbi9saXN0aW5mby9pbWE= ------=_001_NextPart508855211432_=---- Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable =EF=BB=BF
I have seen some similar implemenation= example=20 in the current implementation.
 
To: =C3=86 <=C3=A6@example.com>, =3D?q?iso-8859-= 1?FF=3D? <ff@example.com>
 
Jiankang Yao
 
Date: 2013-09-11 01:17
To: ima
Subject: [EAI] Partly internationalised mail
<= /DIV>
Hi,
 
consider the following field:
 
To: =C3=86 <=C3=A6@example.com>, =C3=85 <= ;ff@example.com>
 
That is indubitably a valid EAI field.&= nbsp;But then consider:
 
To: =C3=86 <=C3=A6@example.com>, =3D?q?iso-8859-= 1?FF=3D? <ff@example.com>
 
I can't remember the 2047 rules, despit= e having implemented them
twice. But you get the point. That = ;is, as far as I can see, valid.
 
Perhaps somewhat surprising. I did not = expect that my code would use
both UTF-8-EAI-ish syntax and 2047 syntax&nb= sp;in the same field. But it
seems valid, and the code is the m= ost straightforward implementation
was the simplest design.
 
Arnt
_______________________________________________
IMA mailing list
IMA@ietf.org
https://www.ietf.org/mailman/listinfo/ima
------=_001_NextPart508855211432_=------ From arnt@gulbrandsen.priv.no Sat Sep 14 08:24:10 2013 Return-Path: X-Original-To: ima@ietfa.amsl.com Delivered-To: ima@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD08411E81E6 for ; Sat, 14 Sep 2013 08:24:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ID9l1BllXV9V for ; Sat, 14 Sep 2013 08:24:10 -0700 (PDT) Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id 235C511E81E4 for ; Sat, 14 Sep 2013 08:24:10 -0700 (PDT) Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 7E7ECFA032E; Sat, 14 Sep 2013 15:24:08 +0000 (UTC) Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.4) with esmtpsa id 1379172247-6490-6488/12/12; Sat, 14 Sep 2013 15:24:07 +0000 From: Arnt Gulbrandsen To: ima@ietf.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) Date: Sat, 14 Sep 2013 17:24:00 +0200 Message-Id: <7hbo3vzasv.fsf@fri.gulbrandsen.priv.no> Subject: [EAI] Generating DSNs X-BeenThere: ima@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "EAI \(Email Address Internationalization\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Sep 2013 15:24:10 -0000 Hi, if, for some reason, I need to generate a DSN, I can either generate the message as is, which may make a DSN that requires SMTPUTF8, or I can chop away bits or downgrade until the DSN is universally acceptable. The former _should_ be safe... right? The envelope sender _ought_ to be able to receive an internationalised DSN. But I'm queasy. I feel there's something I've overlooked. My fingers just don't want commit code that requires an SMTP extension in order to deliver a DSN. Arnt From johnl@iecc.com Sat Sep 14 08:47:12 2013 Return-Path: X-Original-To: ima@ietfa.amsl.com Delivered-To: ima@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46A2611E81FA for ; Sat, 14 Sep 2013 08:47:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.792 X-Spam-Level: X-Spam-Status: No, score=-102.792 tagged_above=-999 required=5 tests=[AWL=-0.193, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 194PsNKMEa5U for ; Sat, 14 Sep 2013 08:47:06 -0700 (PDT) Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id B23BD11E80F6 for ; Sat, 14 Sep 2013 08:47:05 -0700 (PDT) Received: (qmail 79542 invoked from network); 14 Sep 2013 15:47:04 -0000 Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 14 Sep 2013 15:47:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=523484f8.xn--hew.k1309; i=johnl@user.iecc.com; bh=3aYXabYUSDtUMEk/CQtDM0+fkYuq32couOst8+CCJrY=; b=KqgkV7GfRwUvzry4+tgIY7jRJ3DECyWNFhw+bXRiQeCCe5lCCs+SCDegQSPK98t4QSTTaqdYkFEtSCrikcg3g8TAgJfH1u+aGoAiSS6QZ++FticZqi7HTy7xpzYAHZzt+soQbaZO7eK2hKzBi9dgmybl5hIcRhtVVdfvPT6Ph+Qb6MbbfQ6nrkcByHrtC2zLhVP8/Y/+gC8hoe7L+K0iHbbwdCyDwW6nrxa/swwGMTCbVdSy3BI5OZI9ygjV1C+B DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=523484f8.xn--hew.k1309; olt=johnl@user.iecc.com; bh=3aYXabYUSDtUMEk/CQtDM0+fkYuq32couOst8+CCJrY=; b=hremHBkn7RjT+OCtOiNqqksS7lAuIMDtcwFGQdspNL8dzskfUKwGyGQlJaCbGmN0woPb3ZTBYpAPJrpweIwo18bSrmS5EAfJ5JERbmYmgQe2jEEPghc78GKqajyzMfdOye4NEZLisinha0cvHPHkDDU6qNXPuulsZMYFdrEDtXrYeCVUcmivsDjUfoMowmcM2VMTSANMonkm32G6+sD0Jab/mvrChFlCywrJKWWo/hd5WYYs2aJKg6E5ve5Q1muH Date: 14 Sep 2013 15:46:42 -0000 Message-ID: <20130914154642.85535.qmail@joyce.lan> From: "John Levine" To: ima@ietf.org In-Reply-To: <7hbo3vzasv.fsf@fri.gulbrandsen.priv.no> Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Cc: arnt@gulbrandsen.priv.no Subject: Re: [EAI] Generating DSNs X-BeenThere: ima@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "EAI \(Email Address Internationalization\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Sep 2013 15:47:12 -0000 >if, for some reason, I need to generate a DSN, I can either generate the >message as is, which may make a DSN that requires SMTPUTF8, or I can >chop away bits or downgrade until the DSN is universally acceptable. > >The former _should_ be safe... right? The envelope sender _ought_ to be >able to receive an internationalised DSN. You can send an EAI message from an ASCII address, and if you were sufficiently cement-headed, you could even send it from an ASCII address that can't receive EAI mail. But I think we're deep into "don't do that" territory. At that point, it's far more likely to be spam blowback than anything the recipient actually wants. From klensin@jck.com Sat Sep 14 18:47:05 2013 Return-Path: X-Original-To: ima@ietfa.amsl.com Delivered-To: ima@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A11721E8054 for ; Sat, 14 Sep 2013 18:47:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.099 X-Spam-Level: X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ljsgYzhfTd8z for ; Sat, 14 Sep 2013 18:46:59 -0700 (PDT) Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7A10811E80A2 for ; Sat, 14 Sep 2013 18:46:58 -0700 (PDT) Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from ) id 1VL1QQ-0005Xd-Ae; Sat, 14 Sep 2013 21:46:58 -0400 Date: Sat, 14 Sep 2013 21:46:53 -0400 From: John C Klensin To: Arnt Gulbrandsen , ima@ietf.org Message-ID: In-Reply-To: <7hbo3vzasv.fsf@fri.gulbrandsen.priv.no> References: <7hbo3vzasv.fsf@fri.gulbrandsen.priv.no> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: [EAI] Generating DSNs X-BeenThere: ima@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "EAI \(Email Address Internationalization\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Sep 2013 01:47:05 -0000 --On Saturday, September 14, 2013 17:24 +0200 Arnt Gulbrandsen wrote: > Hi, > > if, for some reason, I need to generate a DSN, I can either > generate the message as is, which may make a DSN that requires > SMTPUTF8, or I can chop away bits or downgrade until the DSN > is universally acceptable. > > The former _should_ be safe... right? The envelope sender > _ought_ to be able to receive an internationalised DSN. But > I'm queasy. I feel there's something I've overlooked. Possibly not. There are a number of situations in which an EAI-capable system can be configured in a way that leads to a mess. The most significant one involves a receiving system that uses non-ASCII addresses configuring MX records so that some of the relay alternatives are not EAI-capable. IIR, we warn explicitly against that; I don't think we were as explicit in warning that a host sending out messages with forward-pointing non-ASCII addresses had better be able to accept messages that contain non-ASCII backward-pointing addresses or other header information. Such messages can be generated by "reply" functions, not just as DSNs and are pretty much the same problem either way. > My fingers just don't want commit code that requires an SMTP > extension in order to deliver a DSN. That is a slightly different matter, since, if you are going to send a message with non-ASCII envelope or header material, you pretty much have to handle it as SMTPUTF8 (again, whether it is a DNS or a simple reply). The only thing that makes DSNs special is that I wouldn't lose much sleep or try to go to special trouble if one turns out to be undeliverable because the SMTPUTF8 extension isn't supported: whether the relevant original sender is a spammer (as John Levine suggests) or merely a moron doesn't make much difference. john From yaojk@cnnic.cn Wed Sep 25 02:05:35 2013 Return-Path: X-Original-To: ima@ietfa.amsl.com Delivered-To: ima@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 442A121F9C46 for ; Wed, 25 Sep 2013 02:05:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.333 X-Spam-Level: X-Spam-Status: No, score=-99.333 tagged_above=-999 required=5 tests=[AWL=-1.088, BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LM9H-QsfQRXc for ; Wed, 25 Sep 2013 02:05:31 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id CD21121E8082 for ; Wed, 25 Sep 2013 02:05:21 -0700 (PDT) X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn Received: from unknown127.0.0.1 (HELO healthyao-think) (127.0.0.1) by 127.0.0.1 with SMTP; Wed, 25 Sep 2013 17:05:08 +0800 Date: Wed, 25 Sep 2013 17:05:09 +0800 From: "Jiankang Yao" To: "Arnt Gulbrandsen" References: <7hbo3vzasv.fsf@fri.gulbrandsen.priv.no> X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7.0.1.92[cn] Mime-Version: 1.0 Message-ID: <2013092517050550968035@cnnic.cn> Content-Type: multipart/alternative; boundary="----=_001_NextPart315461443313_=----" Cc: ima Subject: Re: [EAI] Generating DSNs X-BeenThere: ima@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: yaojk List-Id: "EAI \(Email Address Internationalization\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Sep 2013 09:05:35 -0000 This is a multi-part message in MIME format. ------=_001_NextPart315461443313_=---- Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 RGVhciBBcm50IEd1bGJyYW5kc2VuLA0KDQogIE5leHQgeWVhciwgQ05OSUMgd2lsbCBob3N0IGEg d29ya3Nob3AgYWJvdXQgdGhlIGRlcGxveW1lbnQgb2YgbXVsdGktbGFuZ3VhZ2UgZW1haWwgYWRk cmVzcyB0ZWNobm9sb2d5IHVuZGVyIHRoZSBBUEVDIGZyYW1ld29yayAod3d3LmFwZWMub3JnKSBp biBDaGluYSBhcm91bmQgSnVseSAyMDE0Lg0KICAgSWYgeW91ciBpbXBsZW1lbnRhdGlvbiBhYm91 dCBFQUkgaXMgcmVhZHkgYmVmb3JlIG5leHQgTWF5LCB3ZWxjb21lIHRvIGRvIHNvbWUgZGVtbyBv ciBwcmVzZW50YXRpb24gYWJvdXQgeW91ciBpbXBsZW1lbnRhdGlvbiBpbiB0aGF0IHdvcmtzaG9w Lg0KDQpUaGFua3MuDQoNCg0KDQoNCkppYW5rYW5nIFlhbw0KDQpGcm9tOiBBcm50IEd1bGJyYW5k c2VuDQpEYXRlOiAyMDEzLTA5LTE0IDIzOjI0DQpUbzogaW1hDQpTdWJqZWN0OiBbRUFJXSBHZW5l cmF0aW5nIERTTnMNCkhpLA0KDQppZiwgZm9yIHNvbWUgcmVhc29uLCBJIG5lZWQgdG8gZ2VuZXJh dGUgYSBEU04sIEkgY2FuIGVpdGhlciBnZW5lcmF0ZSB0aGUNCm1lc3NhZ2UgYXMgaXMsIHdoaWNo IG1heSBtYWtlIGEgRFNOIHRoYXQgcmVxdWlyZXMgU01UUFVURjgsIG9yIEkgY2FuDQpjaG9wIGF3 YXkgYml0cyBvciBkb3duZ3JhZGUgdW50aWwgdGhlIERTTiBpcyB1bml2ZXJzYWxseSBhY2NlcHRh YmxlLg0KDQpUaGUgZm9ybWVyIF9zaG91bGRfIGJlIHNhZmUuLi4gcmlnaHQ/IFRoZSBlbnZlbG9w ZSBzZW5kZXIgX291Z2h0XyB0byBiZQ0KYWJsZSB0byByZWNlaXZlIGFuIGludGVybmF0aW9uYWxp c2VkIERTTi4gQnV0IEknbSBxdWVhc3kuIEkgZmVlbCB0aGVyZSdzDQpzb21ldGhpbmcgSSd2ZSBv dmVybG9va2VkLg0KDQpNeSBmaW5nZXJzIGp1c3QgZG9uJ3Qgd2FudCBjb21taXQgY29kZSB0aGF0 IHJlcXVpcmVzIGFuIFNNVFAgZXh0ZW5zaW9uDQppbiBvcmRlciB0byBkZWxpdmVyIGEgRFNOLg0K DQpBcm50DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K SU1BIG1haWxpbmcgbGlzdA0KSU1BQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWls bWFuL2xpc3RpbmZvL2ltYQ== ------=_001_NextPart315461443313_=---- Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable
Dear Arnt Gulbrandsen,
 
  Next year, CNNIC will host= a=20 workshop about the deployment of multi-language email address technology u= nder=20 the APEC framework (www.apec.org) in C= hina=20 around July 2014.
   If your implementation ab= out EAI=20 is ready before next May, welcome to do some demo or presentation about yo= ur=20 implementation in that workshop.
 
Thanks.
 
Jiankang Yao
 
Date: 2013-09-14 23:24
To: ima
Subject: [EAI] Generating DSNs
Hi,
 
if, for some reason, I need to gen= erate a DSN, I can either generate the<= /DIV>
message as is, which may make a DS= N that requires SMTPUTF8, or I can
chop away bits or downgrade until the&n= bsp;DSN is universally acceptable.
 
The former _should_ be safe... right? T= he envelope sender _ought_ to be
able to receive an internationalised DSN.&nb= sp;But I'm queasy. I feel there's
something I've overlooked.
 
My fingers just don't want commit code&= nbsp;that requires an SMTP extension
in order to deliver a DSN.
 
Arnt
_______________________________________________
IMA mailing list
IMA@ietf.org
https://www.ietf.org/mailman/listinfo/ima
------=_001_NextPart315461443313_=------