In article <jollyroger-EEC2FB.02424928042008@[EMAIL PROTECTED]
>, Jolly
Roger <jollyroger@[EMAIL PROTECTED]
> wrote:
> In article <280420081814394233%helpful_harry@[EMAIL PROTECTED]
>,
> Helpful Harry <helpful_harry@[EMAIL PROTECTED]
> wrote:
>
> > In article <jollyroger-E0A834.00323128042008@[EMAIL PROTECTED]
>, Jolly
> > Roger <jollyroger@[EMAIL PROTECTED]
> wrote:
> >
> > > There is no attachment, and it's just plain text. Have a look for
> > > yourself:
> > >
> > > Message-ID:
<33344081-90A6-4C31-95CB-F88710A6BBEF%edv@[EMAIL PROTECTED]
>
> > >
> > > As you can see, it's just an ordinary post.
> >
> > 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:
> >
> > Content-Transfer-Encoding: binary
> >
> > which is probably where the problem comes from since it doesn't appear
> > 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.
I no longer care.
Why do I bother?? :o\
Helpful Harry
Hopefully helping harassed humans happily handle handiwork hard****ps ;o)
|
