Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <5.2.1.1.2.20030410160138.024b4998@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
Date: Thu, 10 Apr 2003 16:16:35 -0700
To: cygwin AT cygwin DOT com
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: For The Record: HTML Email on the Internet; RFC 2557
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

To Whom It May Concern,

The IETF publishes this standard for electronic mail on the Internet 
using HTML and even supports resource references in the HTML whose 
targets (images, sounds, etc.) can be incorporated into the same MIME 
message as the HTML body.

In my opinion, it's simply foolish to anchor electronic mail in the 
pre-markup, pre-media days of text-only electronic communication.

Randall Schulz


-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-

RFC 2557
"MIME Encapsulation of Aggregate Documents, such as HTML (MHTML) "

Abstract:
This document a) defines the use of a MIME multipart/related structure 
to aggregate a text/html root resource and the subsidiary resources it 
references, and b) specifies a MIME content-header 
(Content-Location)that allow URIs in a multipart/related text/html root 
body part to reference subsidiary resources in other body parts of the 
same multipart/related structure. [STANDARDS-TRACK]

-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/