Re: Full Headers?

[<balsa microwave com>]

Ok, I cede the point.

Regardless, it really doesnt matter in the context I was using, since the
resrictions on format would all be imposed on the creator of the message.

The feature I was talking about was to just display the full unmodified
source as it is received, regardless of which standard it was created for.
I wasnt talking about the specific syntaxes of the headers, I was simply
referring to the concept of having the message displayed, with all the
headers first, the blank seperator line, and then the body as transmitted
by the underlying structure, WITHOUT any decoding having been applied..

--------
Subject:
Header:
To:
OtherHeader:
From:
X-Etc:

bodybodybody bodybodybody bodybodybody bodybodybody
bodybodybody bodybodybody bodybodybody bodybodybody
bodybodybody bodybodybody bodybodybody bodybodybody
bodybodybody bodybodybody bodybodybody bodybodybody
bodybodybody bodybodybody bodybodybody bodybodybody
bodybodybody bodybodybody bodybodybody bodybodybody
bodybodybody bodybodybody bodybodybody bodybodybody
bodybodybody bodybodybody bodybodybody bodybodybody
..
..
..
..
..
..
..
..
--------


On Tue, 10 Jul 2001, Brian Stafford wrote:

> On Tue, 10 July 16:07 balsa@microwave.com wrote:
> >
> > Er, yes, thats why I mentioned 2822 in parens.. I dont beleive, however,
> > that 2822 makes any significant changes to the format often referred to as
> > "RFC-822" format, other than possibly a rename to "RFC-2822" format..
>
> RFC 2822 clarifies many ambiguities in 822, corrects mistakes, is rather
> less liberal in the permitted syntax of headers.  It devotes 8 pages to
> obsolete syntax and appendix B lists 30 significant changes from earlier
> standards.  Not all valid RFC 822 messages are valid RFC 2822 messages.
>
> Brian Stafford
>