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: <019a01c2ffb8$adbd39c0$b454893e@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <cygwin AT cygwin DOT com>, "Randall R Schulz" <rrschulz AT cris DOT com>
References: <5 DOT 2 DOT 1 DOT 1 DOT 2 DOT 20030410160138 DOT 024b4998 AT pop3 DOT cris DOT com>
Subject: Re: For The Record: HTML Email on the Internet; RFC 2557
Date: Fri, 11 Apr 2003 00:26:55 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Randall R Schulz wrote:
> 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.

There's nothing wrong with HTML mail when used tastefully and in a way which
enhances communication.

Unfortunately, a lot (most?) of the time, HTML mail is used in such a way
that it detracts from the content of the message and is simply a needless
bandwidth sucker.



Max.


--
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/