Re: MIME implementation documentation

Pete Resnick <presnick@qualcomm.com> Fri, 16 August 1996 18:52 UTC

Message-Id: <v0300780dae3a70dcf740@resnick1.isdn.uiuc.edu>
Date: Fri, 16 Aug 1996 13:43:01 -0500
Precedence: bulk
Sender: ietf-archive-request@ietf.org
From: Pete Resnick <presnick@qualcomm.com>
To: John C Klensin <klensin@mail1.reston.mci.net>
Cc: Dave Crocker <dcrocker@brandenburg.com>, Ned Freed <Ned.Freed@innosoft.com>, ietf-822@list.cren.net, Harald.T.Alvestrand@uninett.no
Subject: Re: MIME implementation documentation
In-Reply-To: <SIMEON.9608161323.A@muahost.mail1.reston.mci.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

On 8/16/96 at 12:38 PM -0500, John C Klensin wrote:

>On Fri, 16 Aug 1996 09:43:55 -0500  Pete Resnick
><presnick@qualcomm.com> wrote:
>> Just to name names: I know that Cyberdog on the Macintosh and Microsoft's
>> new mail and news offering (the latter for which I don't know the release
>> status) both produce multipart/alternative by default (without "by-hand"
>> user manipulation) for certain types of messages.
>
>Well, that is considerable progress, although it would be nice
>to know
>  -- what types of messages

Cyberdog sends multipart/alternative containing text/plain and
text/enriched whenever the user puts any styled text into their message.
MS's thing I'm told (I haven't actually gotten one yet) sends mult/alt with
text/plain and text/html, though I'm not sure of the circumstances.

>  -- what really acts on these on receipt, other than treating
>them as "mixed".

Ned mentions metamail and Pine, though I don't know what they do. I know
Mac Eudora 3.0 displays the "best" one (i.e. furthest down the list) that
it can handle.

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