Valdis(_dot_)Kletnieks(_at_)vt(_dot_)edu writes:
Quoting RFC822, section 3.1:
3. LEXICAL ANALYSIS OF MESSAGES
3.1. GENERAL DESCRIPTION
A message consists of header fields and, optionally, a body.
The body is simply a sequence of lines containing ASCII charac-
ters. It is separated from the headers by a null line (i.e., a
line with nothing preceding the CRLF).
OK? You see that second sentence? It says "the body is a sequence of
lines containing ASCII characters". If you have be en putting
something other than ASCII in the body of an RFC822 mail, YOU ARE
VIOLATING RFC822. The mere fact that in your particular application,
it happens to work, does NOT mean that it's legal.
Then, how do you define "ASCII characters"?
Quoting RFC822, section 3.3:
------------------------------------------------------------
3.3. LEXICAL TOKENS
The following rules are used to define an underlying lexical
analyzer, which feeds tokens to higher level parsers. See the
ANSI references, in the Bibliography.
; ( Octal, Decimal.)
CHAR = <any ASCII character> ; ( 0-177, 0.-127.)
------------------------------------------------------------
With this, I can read:
The body is simply a sequence of lines containing ASCII characters.
as:
<< The body is simply a sequence of lines containing characters
<< of the range 0-177 (Octal).
and sending "A B C ESC $ B $ + $ s $ 8 ESC ( B" does not
violate RFC822 (ESC = 033 (octal)). This is what
ISO-2022-JP is doing.
---
Ken'ichi HANDA
handa(_at_)etl(_dot_)go(_dot_)jp