[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] =?UTF-8?B?Rlc6IEFkZGVkIHJlZmVyZW5jZSwgYW5kIHN5bmNoLiBvZiB0ZXJt?= =?UTF-8?B?aW5vbG9neQ==?=
- To: =?UTF-8?B?S2FybHNzb24gS2VudCAtIGtla2E=?= <keka@im.se>
- Subject: Re: [idn] =?UTF-8?B?Rlc6IEFkZGVkIHJlZmVyZW5jZSwgYW5kIHN5bmNoLiBvZiB0ZXJt?= =?UTF-8?B?aW5vbG9neQ==?=
- From: RJ Atkinson <rja@inet.org>
- Date: Sun, 02 Jul 2000 11:38:45 -0400
- Cc: idn@ops.ietf.org
- Delivery-date: Sun, 02 Jul 2000 08:44:59 -0700
- Envelope-to: idn-data@psg.com
As many folks are unable to read anything but plain-text email
and plain-text email is customary for IETF WG lists, I'd ask
folks to please ONLY send plain-text email [1]. We've had a number
of non-plain-text mail messages from MS-Exchange users lately.
Recent updates to MS-Exchange will cause the Exchange server
to send mail out in other formats (MS-RichText, HTML) without
the sender asking for this UNLESS the sender explicitly marks an
outbound message as plain-text-only, so folks using MS-Exchange
might need to take extra effort to cause their mail system to behave
in the manner normal for IETF mailing lists. :-)
Regards,
Ran
rja@inet.org
[1] ISO char sets ought to be interoperable, provided MIME is used;
non-standard (i.e. MS proprietary) char sets aren't interoperable.
Fancy formatting, colour, and font settings aren't very interoperable.