RE: mime implementation (nested bodyparts)
"Dr. Mark K. Joseph" <izzy@nugget.scr.atm.com> Mon, 19 August 1996 18:54 UTC
Received: from ietf.org by ietf.org id aa17165; 19 Aug 96 14:54 EDT
Received: from cnri by ietf.org id aa17161; 19 Aug 96 14:54 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa12315;
19 Aug 96 14:54 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net
(8.6.12/8.6.12) with SMTP id OAA10197; Mon, 19 Aug 1996 14:45:30 -0400
Received: from nugget.scr.atm.com ([206.100.186.2]) by list.cren.net
(8.6.12/8.6.12) with ESMTP id OAA10173 for <ietf-822@list.cren.net>;
Mon, 19 Aug 1996 14:45:15 -0400
Received: from mailman.scr.atm.com (mailman.scr.atm.com [206.100.186.54]) by
nugget.scr.atm.com (8.6.12/8.6.9) with ESMTP id LAA11124 for
<ietf-822@list.cren.net>; Mon, 19 Aug 1996 11:48:59 -0700
Message-Id: <19960819182833.izzy@scr.atm.com>
Date: Mon, 19 Aug 1996 11:38:06 -0700
X-Orig-Sender: owner-ietf-822@list.cren.net
Precedence: bulk
Sender: ietf-archive-request@ietf.org
From: "Dr. Mark K. Joseph" <izzy@nugget.scr.atm.com>
To: ietf-822@list.cren.net
Subject: RE: mime implementation (nested bodyparts)
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="=_19tW07g.bO1996u.N18d000A.r08Y.38:004dc7"
Content-Transfer-Encoding: 7bit
X-Mailer: Emissary V2.01, by Attachmate Corp.
X-Listprocessor-Version: 8.0 -- ListProcessor(tm) by CREN
1. Emissary 2.0 handles the viewing of arbitrary nested bodyparts. It is different in that it does not flatten the nesting out. It shows the next level down as an icon. When the user clicks on that icon the user's entire view of that message changes to the next level down. That is we do not open up another window. The user can move up and down the message by pressing an "Up" button to move up in the message and clicking nested icons to move down. 2. Emissary usually will show all parts of a multipart/alternative except in the case where their is only a text/plan and a text/html bodyparts. Here it will just show the text/html. In showing the user all the bodyparts we put up a small notice telling the user what is going on. We chose this approach because on a PC there is no way for the mail/web client to know of all the installed viewer software the user may have. So if we don't have a built in viewer the user can select some other program he knows of. 3. We automatically generate nested multipart/mixed messages for forwarded messages. We preserve all content-types of a forwarded message, so if it contains a multipart/alternative then we perserve that, but we do not generate mutlipart/alternative, parellel, or disgest by ourselves. 4. We also translate ALL message/external bodyparts into clickable URLs, including mail-server. With a mail-server we generate a mailto WITH parameters. This way the body of the message, as well as its subject can be automatically set by the mailto. We however, show the generated message to the user before we send it out so that he can decide what to do with it. 5. And contrary to what the Netscape Web pages says today Emissary also has full HTML support in its mail and news clients. In fact we had this support way before Netscape had it. In addition, we fully support MULTIPART/RELATED with "cid:" links from a text/html bodypart to bodyparts inside the same message for images and all embedded objects (e.g., gifs, word documents). Such a message can be composed by grabbing a page off the web or from scratch in the compose window. The Emissary mail compose window is a full HTML editor.
- RE: mime implementation (nested bodyparts) Dr. Mark K. Joseph