Julien ÉLIE | 9 Oct 2011 21:27
Favicon

Experiment with UTF-8 in message-IDs


Hi all,

In the IETF working group for IMA (Internationalized eMail Address),
there is a current thread about UTF-8 in message-IDs:
    http://www.ietf.org/mail-archive/web/ima/current/threads.html#04330

Quick references in the thread:

http://www.ietf.org/mail-archive/web/ima/current/msg04430.html
http://www.ietf.org/mail-archive/web/ima/current/msg04344.html
http://www.ietf.org/mail-archive/web/ima/current/msg04345.html
http://www.ietf.org/mail-archive/web/ima/current/msg04420.html
http://www.ietf.org/mail-archive/web/ima/current/msg04422.html

RFC 5536 (USEFOR) currently allows only ASCII characters in message-IDs.

INN 2.4 and INN 2.5 have always rejected message-IDs containing
non-ASCII chars.  (I have not looked at INN 2.3 and before.)  When
a message-ID is not valid per RFC 850/1036/... and now 5536, the
article is rejected.

200 news.trigofacile.com InterNetNews server INN 2.6.0 (20110908 prerelease) ready (transit mode)
IHAVE <© <at> fr>
435 Syntax error in message-ID
MODE READER
200 news.trigofacile.com InterNetNews NNRP server INN 2.6.0 (20111003 prerelease) ready (posting ok)
ARTICLE <© <at> test>
501 Syntax error in message-ID
QUIT
(Continue reading)

Charles Lindsey | 10 Oct 2011 12:21
Picon
Picon

Re: Experiment with UTF-8 in message-IDs


>Hi all,

>In the IETF working group for IMA (Internationalized eMail Address),
>there is a current thread about UTF-8 in message-IDs:
>    http://www.ietf.org/mail-archive/web/ima/current/threads.html#04330

>Quick references in the thread:

>http://www.ietf.org/mail-archive/web/ima/current/msg04430.html
>http://www.ietf.org/mail-archive/web/ima/current/msg04344.html
>http://www.ietf.org/mail-archive/web/ima/current/msg04345.html
>http://www.ietf.org/mail-archive/web/ima/current/msg04420.html
>http://www.ietf.org/mail-archive/web/ima/current/msg04422.html

>RFC 5536 (USEFOR) currently allows only ASCII characters in message-IDs.

>INN 2.4 and INN 2.5 have always rejected message-IDs containing
>non-ASCII chars.  (I have not looked at INN 2.3 and before.)  When
>a message-ID is not valid per RFC 850/1036/... and now 5536, the
>article is rejected.

>My question is:  should we try right now to relax the check so as to allow
>UTF-8 in message-IDs?
>If yes, is there something else to enforce?  (NFC normalization?)

It looks like UTF-8 Message-IDs in mail will start to appear. They would
"mostly work" in news it they happened to be encountered (and might well
route around sites that did awkward things with them). So I suggest simply
removing the check in INN would be a good idea - and likewise similar
(Continue reading)


Gmane