From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Gnus doesn't display all parts of a multipart message
Date: Fri, 20 Jul 2001 11:04:00 -0700 [thread overview]
Message-ID: <2n7kx3pje7.fsf@piglet.jia.vnet> (raw)
In-Reply-To: <873d7sc45p.fsf@lynx.ionific.com> (Hannu Koivisto's message of "19 Jul 2001 18:46:58 +0300")
Hannu Koivisto <azure@iki.fi> writes:
> Greetings,
>
> I got a weird mail from a colleague who uses Outlook. To me it
> seems to be a multipart message where the first part is also a
> multipart message, which consists of two alternative parts (plain
> text and HTML). The rest of the top-level parts are images. The
> top-level multipart message, as far as I can see, is not
> multipart/alternative, but multipart/related, or at least that's
> what I think it should be. Not that I really know what
> multipart/related means, but I can guess :) In any case, Gnus
> displays only the other alternative (text message) from the first
> part but not the other top-level parts (images) so I can't
> save them.
>
> The mail (stored from a buffer gotten with ``C-u g'') is available
> at <http://www.iki.fi/azure/var/bugreports/mimekala.txt>. I have
> edited all the content away -- I hope I didn't fuck up anything
> relevant while doing that (I left some content to all parts).
>
> Perhaps you can tell if there is something wrong with the mail
> (i.e. Outlook is faulty) or that it is ok and those image-parts
> should be displayed (i.e. Gnus is faulty).
Gnus is not faulty but not fully implemented.
(setq gnus-mime-display-multipart-related-as-mixed t) works around the
problem.
ShengHuo
next prev parent reply other threads:[~2001-07-20 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 15:46 Hannu Koivisto
2001-07-20 18:04 ` ShengHuo ZHU [this message]
2001-08-19 19:34 ` Lars Magne Ingebrigtsen
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=2n7kx3pje7.fsf@piglet.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).