From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: MML multipart tag -- what does it do?
Date: Fri, 03 Aug 2001 10:52:33 -0700 [thread overview]
Message-ID: <2nr8utf2u6.fsf@piglet.jia.vnet> (raw)
In-Reply-To: <vafwv4lt7nw.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 03 Aug 2001 18:44:35 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> I think the MML multipart tag needs some more explanation. At least
> to me it's not quite clear what it does.
>
> Okay, the examples in the emacs-mime info file are fairly clear. But
> what they leave open to interpretation: suppose I compose a message,
> and the very first line of the body is a multipart tag, followed by a
> couple of part tags.
>
> What does the whole message look like that comes out?
>
> You see, if I just put several part tags in the body, then I get a
> multipart/mixed message, so maybe the same thing happens with a
> multipart tag.
>
> I kinda suspect that under some circumstances the top-level MML tag
> will become the Content-Type of the whole message, whereas under some
> circumstances the Content-Type of the whole message will me
> multipart/mixed with the MML tags given as `children' of that.
If there are more than one top-level (implicit or explicit) parts in
the message, you will get a multipart/mixed Content-Type.
ShengHuo
next prev parent reply other threads:[~2001-08-03 17:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-03 16:44 Kai Großjohann
2001-08-03 17:35 ` Simon Josefsson
2001-08-03 18:16 ` ShengHuo ZHU
2001-08-03 17:52 ` ShengHuo ZHU [this message]
2001-08-03 19:21 ` Kai Großjohann
2001-08-03 21:05 ` Nuutti Kotivuori
2001-08-04 15:42 ` Florian Weimer
2001-08-04 17:00 ` Simon Josefsson
2001-08-05 16:06 ` Florian Weimer
2001-08-05 19:54 ` Simon Josefsson
2001-08-17 10:57 ` 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=2nr8utf2u6.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).