Re: [EAI] UTF-8 in Message-IDs

"Charles Lindsey" <> Mon, 15 August 2011 09:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4007D21F85C0 for <>; Mon, 15 Aug 2011 02:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Status: No, score=-4.399 tagged_above=-999 required=5 tests=[AWL=-0.952, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 40ra45AKwnSQ for <>; Mon, 15 Aug 2011 02:17:06 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 1D5EA21F85B5 for <>; Mon, 15 Aug 2011 02:17:05 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 2FBC321E91 for <>; Mon, 15 Aug 2011 10:17:48 +0100 (BST)
Received: from (HELO ( (smtp-auth username, mechanism cram-md5) by (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Mon, 15 Aug 2011 10:17:48 +0100
Received: from (localhost []) by (8.13.7/8.13.7) with ESMTP id p7F9Hjdt005253 for <>; Mon, 15 Aug 2011 10:17:47 +0100 (BST)
Date: Mon, 15 Aug 2011 10:17:45 +0100
To: IMA <>
From: "Charles Lindsey" <>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1
MIME-Version: 1.0
References: <> <>
Content-Transfer-Encoding: 8bit
Message-ID: <>
In-Reply-To: <>
User-Agent: Opera Mail/9.25 (SunOS)
X-Gradwell-MongoId: 4e48e43c.3a49-b55-2
X-Gradwell-Auth-Method: mailbox
Subject: Re: [EAI] UTF-8 in Message-IDs
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: Mon, 15 Aug 2011 09:17:07 -0000

On Sat, 13 Aug 2011 23:08:48 +0100, <> wrote:

>> And the "EAI experiment" phase did not test this plan,
>> there's no evidence I'm aware of that UTF-8 in Message-
>> IDs is harmless.
> I'm sure it is not, just as utf-8 in addresses is far from harmless and  
> is
> going to require all sorts of infrastructure changes.
> But I fail to see how this is in any way relevant. We're defining a new  
> message
> format here that *cannot* be downgraded to the old format and retain all
> semantics. This is true irrespective of how message-ids are handled. As  
> such,
> utf-8 in message-ids is a small additional cost.

Yes, but you have to consider all the other protocols using mail-like  
formats and their use of the Message-ID. For exmaple, if EAI were to be  
carried over into Netnews (quite a likely development) it would NOT be  
regarded as a "new message format" since the transport paths for Netnews  
are already 8-bit clean and it would simply be necessary for those who  
wish to take advantage of the new facilities to ensure that their user  
agents were suitably upgraded. There will never be a need for  
"downgrading" except at gateways back into the email system.

But within Netnews the Message-ID plays a crucial role, so it is  
reasonable to ask whether UTF-8 in it would cause problems. According to  
the current standards it would not be allowed, of course, but in practice  
the transport paths might or might not barf. So the question has to be  
asked (and I do not know the answer off the top of my head).

Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131                       
Email:      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5