From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/37428 Path: main.gmane.org!not-for-mail From: Nuutti Kotivuori Newsgroups: gmane.emacs.gnus.general Subject: Re: MML multipart tag -- what does it do? Date: Sat, 04 Aug 2001 00:05:07 +0300 Message-ID: <874rrolurg.fsf@smarttrust.com> References: <2nr8utf2u6.fsf@piglet.jia.vnet> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-Trace: main.gmane.org 1035172846 13829 80.91.224.250 (21 Oct 2002 04:00:46 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 04:00:46 +0000 (UTC) Cc: ding@gnus.org Return-Path: Return-Path: Original-Received: (qmail 25897 invoked from network); 3 Aug 2001 21:05:28 -0000 Original-Received: from smtp.dave.sonera.fi (131.177.130.21) by gnus.org with SMTP; 3 Aug 2001 21:05:28 -0000 Original-Received: from kotivnu1-nb.etela.sonera.fi ([131.177.205.219]:57528 "EHLO oro") by inside.dave.sonera.fi with ESMTP id convert rfc822-to-8bit; Sat, 4 Aug 2001 00:05:08 +0300 Original-Received: from naked by oro with local (Exim 3.31 #1 (Debian)) id 15Sm83-0003YT-00; Sat, 04 Aug 2001 00:05:07 +0300 Original-To: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjohann?=) In-Reply-To: (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 03 Aug 2001 21:21:27 +0200") User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Academic Rigor) Original-Lines: 60 Xref: main.gmane.org gmane.emacs.gnus.general:37428 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:37428 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 and 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 part or something. So any ideas on how this could be made clearer? -- Naked