From: Nuutti Kotivuori <nuutti.kotivuori@smarttrust.com>
Cc: ding@gnus.org
Subject: Re: MML multipart tag -- what does it do?
Date: Sat, 04 Aug 2001 00:05:07 +0300 [thread overview]
Message-ID: <874rrolurg.fsf@smarttrust.com> (raw)
In-Reply-To: <vafofpxrlu0.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 03 Aug 2001 21:21:27 +0200")
Kai Großjohann wrote:
> On Fri, 03 Aug 2001, ShengHuo ZHU wrote:
>
>> If there are more than one top-level (implicit or explicit) parts
>> in the message, you will get a multipart/mixed Content-Type.
>
> Hm. So...
>
> Either the body with its <part> and <multipart> tags is a forest or
> it's a tree. If it's a tree, then the Content-Type of the whole
> message is the same as the root of the tree.
>
> If it's a forest, then the Content-Type of the whole message is
> multipart/mixed.
>
> Is that right?
Probably, if you think it like that. The check is simply:
(cont is the result of mml-parse)
,----
| (if (and (consp (car cont))
| (= (length cont) 1))
| (mml-generate-mime-1 (car cont))
| (mml-generate-mime-1 (nconc (list 'multipart '(type . "mixed"))
| cont)))
`----
So a multipart/mixed part is added to contain the whole parse-tree if
there's more than one top level part.
> But how do we explain this to the user?
"If there is more than one toplevel part, your message is sent as a
multipart/mixed message containing the parts, otherwise the toplevel
part is the content of the message."
Atleast I can't put it better than that. In any case, the normal user
hardly understands anything about multipart/mixed, let alone something
as complicated as this.
And there is a problem on this as well. For example if the user wants
to sign his message, he adds this to the beginning of his message:
<#part sign=pgpmime>
And everything is fine when he sends normal messages. But if his
messages contain multiple parts, that above markup will only sign the
first part. He must write instead:
<#multipart sign=pgpmime>
But if he puts this in a normal message, he will get a multipart/mixed
message with just one part. And I have no idea what would happen with
a <mml> part or something.
So any ideas on how this could be made clearer?
-- Naked
next prev parent reply other threads:[~2001-08-03 21:05 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
2001-08-03 19:21 ` Kai Großjohann
2001-08-03 21:05 ` Nuutti Kotivuori [this message]
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=874rrolurg.fsf@smarttrust.com \
--to=nuutti.kotivuori@smarttrust.com \
--cc=ding@gnus.org \
/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).