From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Wed Oct 20 1999 - 04:26:19 CDT
In <WIeEkOAjJDD4QAK8@turnpike.com> Paul Overell <paulo@turnpike.com> writes:
>>2. Do we want to remove the message/news type, and encourage people
>>to use message/rfc822 instead.
>Yes. We implemented message/news but found it just didn't interwork -
>it gets (correctly) interpreted as application/octet-stream by clients
>that don't recognize message/news. We didn't find any other client that
>supported it. We have now abandoned it in favour of message/rfc822.
That indeed seems a good argument.
>> Either way, there are some remarks
>>to be made about the fate of any UTF-8 characters in headers, but
>>these remarks can be made in the context of either message/news or
>>message/rfc822.
>Until 8 bit headers are permitted in mail we must specify that an
>article within a message/rfc822 MUST have any 8 bit headers recast using
>rfc2047. As rfc2047 can only be applied in some specific circumstances
>we need to extend it so that it can be used in the Newsgroups: and
>Followup-to: headers.
I don't think I would go as far as a MUST, but attention must certainly be
drawn to the problem, especially so as to indicate that even Newsgroup
headers may have RFC 2047 applied to them in case of dire necessity.
But the present text on this subject in the message/news section seems to
cover the situation. Would you be happy with that text, suitably adapted
as indicating the proper way to use message/rfc822?
-- Charles H. Lindsey ---------At Home, doing my own thing------------------------ Email: chl@clw.cs.man.ac.uk Web: http://www.cs.man.ac.uk/~chl Voice/Fax: +44 161 437 4506 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