From: Steinar Bang <sb@metis.no>
Subject: Re: Mule-begot problems
Date: 07 Jan 1998 08:56:05 +0100 [thread overview]
Message-ID: <whg1n0g1ka.fsf@norne.oslo.metis.no> (raw)
In-Reply-To: Stainless Steel Rat's message of "06 Jan 1998 15:16:32 -0500"
>>>>> Stainless Steel Rat <ratinox@peorth.gweep.net>:
>>>>> "FP" == Fabrice Popineau <popineau@esemetz.ese-metz.fr> writes:
FP> Why should 8bits data be encoded in 7bits if the right Mime headers are
FP> stated ?
> Because the MIME specifications say it should, because there are a lot of
> MTAs out there that are not "8-bit clean".
> Can you say "legacy system"?
> That is why all of the RFC 822 extensions that address 8-bit data specify
> that it should be encoded into a 7-bit format before transmission.
Actually, I've been using this technique since I first started using
MIME in 1993, ie. mark text/plain; charset=iso-8859-1 as 8bit, and let
the MTA and the recipient worry about the rest.
The reason? Our (ie. the Norwegian email community's) legacy at that
time, was to use ISO8859-1 characters and just-send-8. If I started
using q-p (or base64 for that matter) on plain text with Norwegian
characters, my correctly marked up article was perceived as broken.
Today I currently have MTAs that does the breaking for me, unless the
MTA they're talking to speaks ESMTP and understands 8BITMIME. What
happens after the first MTA, I don't worry about.
- Steinar
next prev parent reply other threads:[~1998-01-07 7:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-06 20:12 Fabrice.Popineau
[not found] ` <x7d8i55pen.fsf@peorth.gweep.net>
1998-01-06 23:36 ` Jason L Tibbitts III
[not found] ` <x7d8i5tber.fsf@peorth.gweep.net>
1998-01-07 2:07 ` Russ Allbery
[not found] ` <x7zpl93paa.fsf@peorth.gweep.net>
1998-01-07 4:12 ` Russ Allbery
1998-01-07 5:14 ` Richard Coleman
1998-01-07 7:56 ` Steinar Bang [this message]
1998-01-07 11:03 ` Kai Grossjohann
-- strict thread matches above, loose matches on Subject: below --
1998-01-06 10:32 Jon Babcock
1998-01-06 13:28 ` Tore Olsen
1998-01-06 18:26 ` Jon Babcock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=whg1n0g1ka.fsf@norne.oslo.metis.no \
--to=sb@metis.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).