From: Geoff Kuenning <geoff@cs.hmc.edu>
Subject: Re: decoding more complex MIME messages
Date: 30 Dec 2004 02:31:19 +0100 [thread overview]
Message-ID: <pnioegc1sig.fsf@bow.cs.hmc.edu> (raw)
In-Reply-To: <x74qksgd4j.fsf@tarte-tatin.hollytree-house.co.uk>
[ Gnus 5.9.0 on Emacs 21.3.1 ]
I'm also having trouble with nested MIME mail. My structure is a bit
different from David's. One example, generated by Outlook Express
6.00.2900.2180, is:
multipart/related {
multipart/alternative {
text/plain
text/html
}
image/jpeg
}
The other, generated by some Kodak software on a Mac that doesn't
produce an X-Mailer header, is:
multipart/mixed {
multipart/related {
multipart/alternative {
[unspecified content-type containing plain text]
text/html
}
image/jpeg
...
}
}
Gnus 5.9.0 doesn't seem to have mm-w3m-* functions. Is there a place
where I could back-fit David's fix, or am I stuck until I can upgrade
to a newer release?
--
Geoff Kuenning geoff@cs.hmc.edu http://www.cs.hmc.edu/~geoff/
Perl is awk with skin cancer.
-- Henry Spencer
next prev parent reply other threads:[~2004-12-30 1:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 17:17 David Edmondson
2004-10-18 23:03 ` Katsumi Yamaoka
2004-12-30 1:31 ` Geoff Kuenning [this message]
2005-01-05 13:21 ` nnml question G.Ananth Somayaji
2005-01-05 18:54 ` Tassilo Horn
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=pnioegc1sig.fsf@bow.cs.hmc.edu \
--to=geoff@cs.hmc.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).