From: david.goldberg6@verizon.net (David S. Goldberg)
Subject: Re: Improper handling of some mime types
Date: Thu, 14 Feb 2002 12:54:31 -0500 [thread overview]
Message-ID: <m1bk7tg9cfc.fsf@blackbird.mitre.org> (raw)
In-Reply-To: <m26650dmsa.fsf@kurt.swanson> (Kurt Swanson's message of "14 Feb 2002 08:57:09 -0800")
>>>>> On 14 Feb 2002 08:57:09 -0800, Kurt Swanson
>>>>> <direct@reply.not.desired> said:
> To me this is a *serious* error. There are two mime parts in
> message-id: tQCa8.5559$qt6.469306@newsread2.prod.itd.earthlink.net in
> the alt.binaries.pictures.orchid newsgroup.
I can't see any binary groups from where I am now, but I'll speculate
since I've seen this type of structure enough times that I bet it's
what's actually in that article. What you're seeing is a structure
like this
1: Multipart/alternative
a) text/plain
b) multipart/related
i) text/html
ii) image/somethingorother
thus the image is actually associated with part 1b, not another part
separate from the multipart/alternative. In general images don't
relate to text/plain; the nominal purpose of multipart/alternative is
to allow a message to do something "reasonable" on both rich and poor
displays. I agree it's annoying since depending on your Emacs
version, gnus can display an image along with text/plain, but I
believe it is correct behavior for the MIME parser. This is why I add
multipart/alternative to gnus-buttonized-mime-types.
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2002-02-14 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2wuxgg8ab.fsf@kurt.swanson>
2002-02-14 8:35 ` Kai Großjohann
[not found] ` <m26650dmsa.fsf@kurt.swanson>
2002-02-14 17:25 ` Kai Großjohann
[not found] ` <m2664zdipf.fsf@kurt.swanson>
2002-02-14 18:38 ` ShengHuo ZHU
2002-02-14 17:32 ` ShengHuo ZHU
2002-02-14 17:39 ` David S. Goldberg
2002-02-14 17:54 ` David S. Goldberg [this message]
[not found] ` <m2adubdis3.fsf@kurt.swanson>
2002-02-15 9:09 ` Kai Großjohann
2002-02-14 18:00 ` Karl Kleinpaste
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1bk7tg9cfc.fsf@blackbird.mitre.org \
--to=david.goldberg6@verizon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).