Re: MIME implementation documentation

Pete Resnick <presnick@qualcomm.com> Sun, 18 August 1996 04:20 UTC

Message-Id: <v03007814ae3c452a0cd4@resnick1.isdn.uiuc.edu>
Date: Sat, 17 Aug 1996 23:13:38 -0500
Precedence: bulk
Sender: ietf-archive-request@ietf.org
From: Pete Resnick <presnick@qualcomm.com>
To: Harald.T.Alvestrand@uninett.no
Cc: ietf-822@list.cren.net, moore@cs.utk.edu
Subject: Re: MIME implementation documentation
In-Reply-To: <23913.840267370@domen.uninett.no>
References: Your message of "Fri, 16 Aug 1996 15:10:43 PDT." <01I8CJGV6XIU8Y507E@INNOSOFT.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

On 8/17/96 at 2:36 AM -0500, Harald.T.Alvestrand@uninett.no wrote:

>Are Nested Body Parts widely implemented?

I have one example from Macintosh Eudora 3.0, but it is sort of a special
cased example: Mac Eudora 3.0 handles (and in fact expects) reception of
nested multiparts when it comes to multipart/digest. If someone sends a
multipart/mixed where the first part is a text/plain (or text/*) and the
second part is a multipart/digest, Eudora will create a mail message in the
In-box with the text/* part and an icon for an attached mailbox. When the
attachment is opened, inside are the contents of the multipart/digest, each
as a seperate mailbox entry, and those can themselves be any sort of
message, including multipart messages which are handled recursively.

We don't do any other particular sort of special handling for nested
multiparts.

Though never released, we do have some code which will generate
multipart/digests within multipart/mixed, but I don't know if that would
count toward operational experience.

>Are External Body Parts widely implemented?

Again, Mac Eudora (perhaps even prior to 3.0; I don't remember) provides a
datapoint, both for reception and generation. For the 'ftp' access-type,
Eudora receives it as a Macintosh bookmark type attachment which is used by
the FTP clients on the Macintosh. When the icon for the bookmark attachment
is double-clicked in the message, Eudora causes the users FTP client to be
launched and download the file (or display the directory). A user can also
send a bookmark and Eudora encodes it as a message/external-body with the
'ftp' access-type.

For the 'mail-server' access-type, Eudora receives them as Eudora mail
stationery attachments. When double-clicked, these cause Eudora to create a
new mail message with the information provided in the phantom body of the
external-body. If a user attaches these stationery files to a message,
Eudora encodes them as message/external-body with the 'mail-server'
access-type.

pr

--
Pete Resnick <mailto:presnick@qualcomm.com>
QUALCOMM Incorporated
Work: (217)337-6377 / Fax: (217)337-1980

Re: MIME implementation documentation Bart Schaefer
Re: MIME implementation documentation Chris Newman
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation Bart Schaefer
Re: MIME implementation documentation Chris Newman
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation John C Klensin
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation John C Klensin
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation Pete Resnick
Re: MIME implementation documentation John C Klensin
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation John C Klensin
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Rens Troost
Re: MIME implementation documentation Pete Resnick
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation Pete Resnick
Re: MIME implementation documentation Jamie Zawinski
Re: MIME implementation documentation Pete Resnick
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation ruth moulton
Re: MIME implementation documentation maf
Re: MIME implementation documentation Larry Masinter
Re: MIME implementation documentation Dave Crocker
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation Valdis.Kletnieks
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation Ned Freed
Re: MIME implementation documentation ruth moulton
Re: MIME implementation documentation John C Klensin
Re: MIME implementation documentation Harald.T.Alvestrand
Re: MIME implementation documentation Valdis.Kletnieks