> > There is no attachment, and it's just plain text. Have a look for
> > yourself:
[quoted text clipped - 4 lines]
>
> It's not a plain text message.
WRONG. It absolutely *is* a plain text message. The included
Content-Type header says so:
Content-Type: text/plain
> Looking at the headers for the original
> post shows:
[quoted text clipped - 4 lines]
> on ANY other message in ANY newsgroup I visit, and that must be a
> "problem" with the original person's newsreader, not mine.
Wrong again. The Content-Transfer-Encoding header is a MIME header that:
(a) indicates whether or not a binary-to-text encoding scheme has been
used on top of the original encoding as specified within the
Content-Type header
(b) if such a binary-to-text encoding method has been used, states which
one.
The RFC (http://www.faqs.org/rfcs/rfc2045.html) defines these values for
Content-Transfer-Encoding: 7bit, quoted printable, base64, 8bit, and
binary. '7bit', '8bit', and 'binary' mean that no binary-to-text
encoding on top of the original encoding was used. In other words, no
other encoding than text/plain was used in this message. In other words,
it's a plain text message.

Signature
Please send all responses to the relevant news group. E-mail sent to
this address may be devoured by my very hungry SPAM filter. I do not
read posts from Google Groups. Use a real news reader if you want me to
see your posts.
JR
Helpful Harry - 28 Apr 2008 22:04 GMT
> > > There is no attachment, and it's just plain text. Have a look for
> > > yourself:
[quoted text clipped - 34 lines]
> other encoding than text/plain was used in this message. In other words,
> it's a plain text message.
I no longer care.
Why do I bother?? :o\
Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)