RE: text/enriched

Article View: a2i.lists.inet-access

Article #5697

Back to a2i.lists.inet-access Previous Next

#5697

From: Inet-Access
Date: Mon, 24 Nov 1997 00:00

12 lines
803 bytes


> The IETF won't define what is acceptable netiquette (eg, sending 
> multipart/alternative instead of only text/enriched).
> 
Although any decent standard should have some instruments for graceful
degradation (backwards compatibility).

But like a said previosly, proper netiquette goes way beyond adherence
to standards.

	Matt

Technical Details

Message-ID: <inet-access.33CCFE438B9DD01192E800A024C84A190D8716@mossbay.chaffeyhomes.com>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f61c3,5a5cad552d303901
X-Google-Attributes: gidf61c3,public
From: Inet-Access <inet-access@lists.ecosystems.net>
Subject: RE: text/enriched
Date: 1997/11/24
Message-ID: <inet-access.33CCFE438B9DD01192E800A024C84A190D8716@mossbay.chaffeyhomes.com>
X-Deja-AN: 292400856
X-To: "'inet-access@earth.com'" <inet-access@earth.com>
Reply-To: inet-access@earth.com
Newsgroups: a2i.lists.inet-access