From: Richard Coleman <coleman@math.gatech.edu>
Subject: Re: Latin 1 in non-MIME news postings?
Date: Thu, 03 Sep 1998 16:48:30 -0400 [thread overview]
Message-ID: <199809032048.QAA05695@math.gatech.edu> (raw)
In-Reply-To: Your message of "03 Sep 1998 13:03:17 EDT." <x7k93lw2lm.fsf@peorth.gweep.net>
> Vanilla MIME is 100% compliant with RFC 822. 8-bit data is *NOT* allowed
> in a MIME message; it must be encoded into a 7-bit format. MIME is
> completely legal in news.
>
> SMTP added the '8bit' transfer type. This is not a MIME standard type...
> that is, it is a standard MIME type for SMTP, not for MIME. That being the
> case, 8bit is valid *ONLY* for SMTP traffic.
This is not correct. RFC2045 clearly defines the type "8bit" as a valid
Content-Transfer-Encoding. Here is one of the relevant paragraphs from
RFC2045:
The Content-Transfer-Encoding values "7bit", "8bit", and "binary" all
mean that the identity (i.e. NO) encoding transformation has been
performed. As such, they serve simply as indicators of the domain of
the body data, and provide useful information about the sort of
encoding that might be needed for transmission in a given transport
system. The terms "7bit data", "8bit data", and "binary data" are
all defined in Section 2.
The MIME standard does not force 7bit transport.
--
Richard Coleman
coleman@math.gatech.edu
next prev parent reply other threads:[~1998-09-03 20:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-02 7:33 Kai Grossjohann
1998-09-02 9:49 ` Jost Krieger
1998-09-02 11:24 ` Kai Grossjohann
1998-09-03 10:15 ` Russ Allbery
[not found] ` <x7soi9yx8s.fsf@peorth.gweep.net>
1998-09-03 16:47 ` Russ Allbery
[not found] ` <x7k93lw2lm.fsf@peorth.gweep.net>
1998-09-03 17:22 ` Russ Allbery
1998-09-03 20:48 ` Richard Coleman [this message]
1998-09-03 17:35 ` Karl Kleinpaste
1998-09-03 10:27 ` Hrvoje Niksic
1998-09-02 10:42 ` jean-luc cassel
1998-09-02 12:25 ` Lars Magne Ingebrigtsen
1998-09-07 20:15 ` Kai Grossjohann
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=199809032048.QAA05695@math.gatech.edu \
--to=coleman@math.gatech.edu \
/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).