Hi Charles,
At 07:16 28-08-2007, Charles Lindsey wrote:
An RFC2822 parser that will not accept SP after the ':' will already be
non-compliant, and will still be non-compliant even if absence of that SP
is relegated to the obs-syntax. Moreover, since 99.999% of emails
currently sent already include that SP, such a parser would be totally
useless in the current email environment - so I think we can safely assume
that no such parser exists.
We don't know the current email environment. Each of us sees a
subset of it. Put together, we get a better picture of it but we
still don't have the whole picture. I, for one, would not assume
that no such parser exists.
An existing RFC2822 agent that currently _generates_ headers without that
SP (I am not aware of any) would then become non-compliant, but the
messages it generated would still be accepted by all current and future
2822-bis-compliant agents.
I thought that the aim of this update to RFC 2822 was not to make
existing implementations non-compliant.
Regards,
-sm