Re: Parsing the Injection-Info: header field

On Sat, Jan 09, 2010 at 11:22:45AM +0100, Julien =C9LIE wrote:
> Yet, RFC 5322 mentions in its introduction:
>=20
>   This document specifies a syntax only for text messages.  In
>   particular, it makes no provision for the transmission of images,
>   audio, or other sorts of structured data in electronic mail messages.
>   There are several extensions published, such as the MIME document
>   series ([RFC2045], [RFC2046], [RFC2049]), which describe mechanisms
>   for the transmission of such data through electronic mail, either by
>   extending the syntax provided here or by structuring such messages to
>   conform to this syntax.  Those mechanisms are outside of the scope of
>   this specification.
>=20
> I understand that RFC 2045 now extends the syntax of RFC 5322 (instead
> of RFC 822).

That interpretation would mean that suddenly CFWS beciame forbidden in MI=
ME
constructs when RFC 2822 was published.  I don't think that was the inten=
t,
especially when "those mechanisms are outside of the scope".

That paragraph is a bit unfortunately worded, though.

--=20
Antti-Juhani Kaijanaho, Jyv=E4skyl=E4, Finland
http://antti-juhani.kaijanaho.fi/newblog/
http://www.flickr.com/photos/antti-juhani/