From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Mon Jul 02 2001 - 06:50:26 CDT
In <20010629235928.B13209@litterbox.meowing.net> greg andruk <gja@meowing.net> writes:
>> I know of no relaying or serving system that would have any technical
>> problem with UTF-8 in headers.
>Ah, that explains why when I created a moderated alt.* group on my test
>server and posted to it, the bounce that came back showed that the
>article could not be delivered to a different address than the one
>where I sent it. The high bits were all stripped off. Right, no
>compatibility problems at all.
Yes, we know there is a problem with moderated groups using UTF-8
characters. But we also know that general solutions will appear as a
result of the IDN efforts, so that it will eventually be possible to mail
to dk-test-blåbærgrød@moderators.isc.org. So if any particular hierarchy
wants to create a moderated group, it might be better for it to hold off
for a while. But that is no reason not to have unmoderated groups.
In any case, the current draft explicitly states that finding a
moderator's address is outside our scope, and the only mention of the
"replace '.' by '-' trick" is in a NOTE.
>>
>> If you are referring to the RFC 2047 machinery, then it is already well
>> established that it is totally unsuitable for newsgroup-names. The
>> interoperability problems are horrendous. Note that the nntp-base document
>> is also taking the UTF-8 route.
>No, I am referring to the LISTPNAMES extension from the NNTP working
>group. It took me about half an hour to add it to INN, including
>compilation and working out the LIST EXTENSIONS whitespace problem.
I cannot find any such extension in RFC 2980. Please be more specific.
-- Charles H. Lindsey ---------At Home, doing my own thing------------------------ Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl Email: chl@clw.cs.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