From owner-ietf-usefor@mail.imc.org Sun Oct 9 12:28:45 2011 Return-Path: X-Original-To: ietfarch-usefor-archive@ietfa.amsl.com Delivered-To: ietfarch-usefor-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF2A21F8B0A for ; Sun, 9 Oct 2011 12:28:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.453 X-Spam-Level: X-Spam-Status: No, score=0.453 tagged_above=-999 required=5 tests=[BAYES_50=0.001, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_UTF8=0.152] 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 Kinx6e9mAurH for ; Sun, 9 Oct 2011 12:28:44 -0700 (PDT) Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 363CF21F8AFF for ; Sun, 9 Oct 2011 12:28:43 -0700 (PDT) Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p99JRKVQ015702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 9 Oct 2011 12:27:21 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id p99JRKV2015701; Sun, 9 Oct 2011 12:27:20 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org) X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-ietf-usefor@mail.imc.org using -f Received: from denver.dinauz.org (denver.dinauz.org [91.121.7.193]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p99JRJfx015682 for ; Sun, 9 Oct 2011 12:27:20 -0700 (MST) (envelope-from julien@trigofacile.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id 850818169 for ; Sun, 9 Oct 2011 21:27:17 +0200 (CEST) Received: from denver.dinauz.org ([127.0.0.1]) by localhost (denver.dinauz.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RDygRrS+Q48V for ; Sun, 9 Oct 2011 21:27:17 +0200 (CEST) Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-552-1-100-186.w83-199.abo.wanadoo.fr [83.199.211.186]) by denver.dinauz.org (Postfix) with ESMTPSA id 51E2F8168 for ; Sun, 9 Oct 2011 21:27:17 +0200 (CEST) Message-ID: <4E91F594.40205@trigofacile.com> Date: Sun, 09 Oct 2011 21:27:16 +0200 From: =?ISO-8859-1?Q?Julien_=C9LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; fr; rv:1.9.2.23) Gecko/20110920 Thunderbird/3.1.15 MIME-Version: 1.0 To: ietf-usefor@imc.org Subject: Experiment with UTF-8 in message-IDs Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-ietf-usefor@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: 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 <©@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 <©@test> 501 Syntax error in message-ID QUIT 205 Bye! (Note that 435 is answered to IHAVE for legacy reasons; 501 should be the real response code per RFC 3977.) 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?) Of course, other requirements from RFC 5536 will remain (that is to say no comments in the Message-ID: header field, and no ">" or WSP). U+00A0 (  in HTML) and other spaces encoded in UTF-8 are allowed, aren't they? We plan on releasing INN 2.5.3 soon, so perhaps we can relax the check starting from INN 2.5.3. I will ask in the INN workers mailing-list, if naturally there is no complaints in this USEFOR mailing-list against going this way. -- Julien ÉLIE « I don't know if it's what you want, but it's what you get. » (Larry Wall) From owner-ietf-usefor@mail.imc.org Mon Oct 10 04:23:30 2011 Return-Path: X-Original-To: ietfarch-usefor-archive@ietfa.amsl.com Delivered-To: ietfarch-usefor-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F124721F8569 for ; Mon, 10 Oct 2011 04:23:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.847 X-Spam-Level: X-Spam-Status: No, score=-0.847 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152] 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 kRo40xaMVTKk for ; Mon, 10 Oct 2011 04:23:28 -0700 (PDT) Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5134121F8573 for ; Mon, 10 Oct 2011 04:23:28 -0700 (PDT) Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p9ABCAM3054169 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Oct 2011 04:12:10 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id p9ABCAQH054168; Mon, 10 Oct 2011 04:12:10 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org) X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-ietf-usefor@mail.imc.org using -f Received: from outbound-queue-2.mail.thdo.gradwell.net (outbound-queue-2.mail.thdo.gradwell.net [212.11.70.35]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p9ABC8K6054140 for ; Mon, 10 Oct 2011 04:12:09 -0700 (MST) (envelope-from news@clerew.man.ac.uk) Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-2.mail.thdo.gradwell.net (Postfix) with ESMTP id E96AF21EC1 for ; Mon, 10 Oct 2011 12:12:06 +0100 (BST) Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Mon, 10 Oct 2011 12:12:06 +0100 Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id p9ABC3QO003880 for ; Mon, 10 Oct 2011 12:12:03 +0100 (BST) Received: (from news@localhost) by clerew.man.ac.uk (8.13.7/8.13.7/Submit) id p9ABC28u003877 for ietf-usefor@imc.org; Mon, 10 Oct 2011 12:12:03 +0100 (BST) To: ietf-usefor@imc.org Xref: clerew local.usefor:25249 Path: clerew!chl From: "Charles Lindsey" Subject: Re: Experiment with UTF-8 in message-IDs Message-ID: X-Newsreader: NN version 6.5.2 (NOV) Date: Mon, 10 Oct 2011 10:21:54 GMT Lines: 70 X-Gradwell-MongoId: 4e92d306.5333-7f7d-2 X-Gradwell-Auth-Method: mailbox X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk Sender: owner-ietf-usefor@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: >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 checks on other headers (but not Date:, I think). It is simply a matter of "being liberal in what you accept", which is a fine thing to do except when it is obviously going to lead to breakage. But I wouldn't do anything about normalization at this stage. That problem only arises if intermediate sites try to rewrite (or "improve") what they received, and that would likely do more harm than good. And, as the EAI standards seem about to become proposed standards, perhaps it is time to revive the idea of UTF-8 in Newsgroup names. There are some early Usefor drafts proposing how it should be done, and they DID contain severe restrictions on allowed characters and strict NFC normalization (but essentially to be enforced at submission time, and left strictly alone thereafter). >Of course, other requirements from RFC 5536 will remain (that is to say >no comments in the Message-ID: header field, and no ">" or WSP). >U+00A0 (  in HTML) and other spaces encoded in UTF-8 are allowed, >aren't they? Even RFC 5332 does not allow comments or WSP ARAIR. >We plan on releasing INN 2.5.3 soon, so perhaps we can relax the check >starting from INN 2.5.3. I will ask in the INN workers mailing-list, >if naturally there is no complaints in this USEFOR mailing-list against >going this way. -- Charles H. Lindsey ---------At Home, doing my own thing------------------------ Tel: +44 161 436 6131 Web: http://www.cs.man.ac.uk/~chl Email: chl@clerew.man.ac.uk 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 From 0-onc1256df2.005af381@schunk.de Sat Oct 15 05:18:02 2011 Return-Path: <0-onc1256df2.005af381@schunk.de> X-Original-To: ietfarch-usefor-archive@ietfa.amsl.com Delivered-To: ietfarch-usefor-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6797D21F8B2B for ; Sat, 15 Oct 2011 05:18:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -27.238 X-Spam-Level: X-Spam-Status: No, score=-27.238 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_SBL=20, URIBL_WS_SURBL=10, 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 Su5Ol4ZJ2bju for ; Sat, 15 Oct 2011 05:18:02 -0700 (PDT) Received: from vodafone.it (net-93-65-184-93.cust.dsl.vodafone.it [93.65.184.93]) by ietfa.amsl.com (Postfix) with ESMTP id C6BCC21F8B1D for ; Sat, 15 Oct 2011 05:18:01 -0700 (PDT) Received: from 93.65.184.93(helo=ietf.org) by ietf.org with esmtpa (Exim 4.69) (envelope-from ) id 1MM0HE-8650sd-AP for ; Sat, 15 Oct 2011 13:18:01 +0100 From: To: Subject: Looking for my Prince Date: Sat, 15 Oct 2011 13:18:01 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Mailer: zjjaporwbv 33 Message-ID: <4146891223.N16ANW5L875241@osrigrypotpyotc.chrdynyhriaub.info> ciao, my dear reader! The reduction of the universe to a single being, the expansion of a single being even to God, this is love. Hello Honey! I would like to tell you a bit about myself. I'm tall with a middle figure. I have long blond, very beautiful hair, small nice nose, perfect lips and big blue eyes. I am a sociable easy going person, so I like meeting friends, going out, have fun and new something interesting. I'm looking for a strong relations with a caring and smart man! I am really tired of all these temporary relations. I would like to find a man who will be able to estimate not only my beauty, but also my brain and my soul... I want him to kind and handsome, brave and tender, romantic and honest. my site: www.want4love.ru number-one, kisses Klaudia From online1025544@telkomsa.net Sun Oct 30 12:57:24 2011 Return-Path: X-Original-To: ietfarch-usefor-archive@ietfa.amsl.com Delivered-To: ietfarch-usefor-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71CF121F8B4D; Sun, 30 Oct 2011 12:57:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.445 X-Spam-Level: X-Spam-Status: No, score=0.445 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, US_DOLLARS_3=0.63] 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 HB57uZ2rCV-v; Sun, 30 Oct 2011 12:57:24 -0700 (PDT) Received: from draco.telkomsa.net (draco.telkomsa.net [196.25.211.120]) by ietfa.amsl.com (Postfix) with ESMTP id 01DF921F8B4C; Sun, 30 Oct 2011 12:57:24 -0700 (PDT) Received: from mail8.telkomsa.net (unknown [192.168.16.221]) by draco.telkomsa.net (Postfix) with ESMTP id AAC30A876E; Sun, 30 Oct 2011 21:57:22 +0200 (SAST) Date: Sun, 30 Oct 2011 21:57:22 +0200 (SAST) From: Joseph William Reply-To: Joseph William Message-ID: <925883987.1720588.1320004642691.JavaMail.root@zimbra8-vm1.telkomsa.net> Subject: Loan Offer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.16.42] X-Mailer: Zimbra 6.0.10_GA_2692 (zclient/6.0.10_GA_2692) To: undisclosed-recipients:; Loan Offer Do you need a loan? Arrangements to Borrow up to $10,000,000.00 Choose between 1 to 25 years repayment period. Choose between monthly and annual repayment plan Flexible loan terms and conditions. All these plans and more on contacting us. Please apply by sending your email to the contact below. Agent Name: *Joseph William Agent Email: *josephloanoffer2011@gmail.com Regards Online Sec Management. Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p9ABCAM3054169 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Oct 2011 04:12:10 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id p9ABCAQH054168; Mon, 10 Oct 2011 04:12:10 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org) X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-ietf-usefor@mail.imc.org using -f Received: from outbound-queue-2.mail.thdo.gradwell.net (outbound-queue-2.mail.thdo.gradwell.net [212.11.70.35]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p9ABC8K6054140 for ; Mon, 10 Oct 2011 04:12:09 -0700 (MST) (envelope-from news@clerew.man.ac.uk) Received: from outbound-edge-2.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-2.mail.thdo.gradwell.net (Postfix) with ESMTP id E96AF21EC1 for ; Mon, 10 Oct 2011 12:12:06 +0100 (BST) Received: from port-89.xxx.th.newnet.co.uk (HELO clerew.man.ac.uk) (80.175.135.89) (smtp-auth username postmaster%pop3.clerew.man.ac.uk, mechanism cram-md5) by outbound-edge-2.mail.thdo.gradwell.net (qpsmtpd/0.83) with (DES-CBC3-SHA encrypted) ESMTPSA; Mon, 10 Oct 2011 12:12:06 +0100 Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id p9ABC3QO003880 for ; Mon, 10 Oct 2011 12:12:03 +0100 (BST) Received: (from news@localhost) by clerew.man.ac.uk (8.13.7/8.13.7/Submit) id p9ABC28u003877 for ietf-usefor@imc.org; Mon, 10 Oct 2011 12:12:03 +0100 (BST) To: ietf-usefor@imc.org Xref: clerew local.usefor:25249 Path: clerew!chl From: "Charles Lindsey" Subject: Re: Experiment with UTF-8 in message-IDs Message-ID: X-Newsreader: NN version 6.5.2 (NOV) Date: Mon, 10 Oct 2011 10:21:54 GMT Lines: 70 X-Gradwell-MongoId: 4e92d306.5333-7f7d-2 X-Gradwell-Auth-Method: mailbox X-Gradwell-Auth-Credentials: postmaster@pop3.clerew.man.ac.uk Sender: owner-ietf-usefor@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: >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 checks on other headers (but not Date:, I think). It is simply a matter of "being liberal in what you accept", which is a fine thing to do except when it is obviously going to lead to breakage. But I wouldn't do anything about normalization at this stage. That problem only arises if intermediate sites try to rewrite (or "improve") what they received, and that would likely do more harm than good. And, as the EAI standards seem about to become proposed standards, perhaps it is time to revive the idea of UTF-8 in Newsgroup names. There are some early Usefor drafts proposing how it should be done, and they DID contain severe restrictions on allowed characters and strict NFC normalization (but essentially to be enforced at submission time, and left strictly alone thereafter). >Of course, other requirements from RFC 5536 will remain (that is to say >no comments in the Message-ID: header field, and no ">" or WSP). >U+00A0 (  in HTML) and other spaces encoded in UTF-8 are allowed, >aren't they? Even RFC 5332 does not allow comments or WSP ARAIR. >We plan on releasing INN 2.5.3 soon, so perhaps we can relax the check >starting from INN 2.5.3. I will ask in the INN workers mailing-list, >if naturally there is no complaints in this USEFOR mailing-list against >going this way. -- Charles H. Lindsey ---------At Home, doing my own thing------------------------ Tel: +44 161 436 6131 Web: http://www.cs.man.ac.uk/~chl Email: chl@clerew.man.ac.uk 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 Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p99JRKVQ015702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 9 Oct 2011 12:27:21 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org) Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id p99JRKV2015701; Sun, 9 Oct 2011 12:27:20 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org) X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-ietf-usefor@mail.imc.org using -f Received: from denver.dinauz.org (denver.dinauz.org [91.121.7.193]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p99JRJfx015682 for ; Sun, 9 Oct 2011 12:27:20 -0700 (MST) (envelope-from julien@trigofacile.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by denver.dinauz.org (Postfix) with ESMTP id 850818169 for ; Sun, 9 Oct 2011 21:27:17 +0200 (CEST) Received: from denver.dinauz.org ([127.0.0.1]) by localhost (denver.dinauz.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RDygRrS+Q48V for ; Sun, 9 Oct 2011 21:27:17 +0200 (CEST) Received: from MacBook-Pro-de-Julien-Elie.local (AAubervilliers-552-1-100-186.w83-199.abo.wanadoo.fr [83.199.211.186]) by denver.dinauz.org (Postfix) with ESMTPSA id 51E2F8168 for ; Sun, 9 Oct 2011 21:27:17 +0200 (CEST) Message-ID: <4E91F594.40205@trigofacile.com> Date: Sun, 09 Oct 2011 21:27:16 +0200 From: =?ISO-8859-1?Q?Julien_=C9LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; fr; rv:1.9.2.23) Gecko/20110920 Thunderbird/3.1.15 MIME-Version: 1.0 To: ietf-usefor@imc.org Subject: Experiment with UTF-8 in message-IDs Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-ietf-usefor@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: 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 <©@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 <©@test> 501 Syntax error in message-ID QUIT 205 Bye! (Note that 435 is answered to IHAVE for legacy reasons; 501 should be the real response code per RFC 3977.) 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?) Of course, other requirements from RFC 5536 will remain (that is to say no comments in the Message-ID: header field, and no ">" or WSP). U+00A0 (  in HTML) and other spaces encoded in UTF-8 are allowed, aren't they? We plan on releasing INN 2.5.3 soon, so perhaps we can relax the check starting from INN 2.5.3. I will ask in the INN workers mailing-list, if naturally there is no complaints in this USEFOR mailing-list against going this way. -- Julien ÉLIE « I don't know if it's what you want, but it's what you get. » (Larry Wall)