[Top] [All Lists]

Re: Restrictions on the Content-Type "message"

1999-01-05 10:13:06

I read all of Ned's interesting replies on this topic, observed that
they had all been CCed to usenet-format(_at_)clari(_dot_)net, and deleted them,
intending to deal with them when I dealt with the day's postings to
the usenet-format list (which I have gated to a local newsgroup on my

Then I go to my local newsgroup and they are not there :-(. Presumably
because, due to anti-spam measures, Ned does not have posting privileges
to the list. Cc to Brad to ask him to fix this, so at least Ned can post
to the list. I would also hope he would subscribe to it, at least while
this present thread runs. (email to usenet-format-request(_at_)clari(_dot_)net 
subscribe your-email-address in the body).

So could anybody who still has copies let me have them, or better post
them to the list?

BTW, what is ietf-822(_at_)imc(_dot_)org? Some RFC822-email list I presume. 
it continue to be included in these exchanges?

So, dealing with the points raised as best I can remember them, Ned
seems to be suggesting that it is possible to cope with headers with
8bit characters in them within the existing message structure, even
within message/rfc822. But I just do not see how this is possible. So
please can we have an explanation of how it's done, preferably with a
simple example. I agree it would be far better to use a message type
if it can be done, and using an application type was known to be a
second-best kludge when it was put forward.

Charles H. Lindsey ---------At Home, doing my own thing------------------------
Email:     chl(_at_)clw(_dot_)cs(_dot_)man(_dot_)ac(_dot_)uk  Web:
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