Re: Syntax validation of articles by injecting agents

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In message <[email protected]>, Charles Lindsey
<[email protected]> writes

>But I don't think RFC 2049 ever intended to imply that MIME-Version was
>needed for a message that did not actually use any of the MIME features.

Hardly on topic for this list, but yes that's exactly what it means, and
what it was intended to mean.  It's no big deal for a client to generate
the header field, so it's hardly onerous!  (see this message for an
example of a compliant client)

What it does for you is to ensure that if you are corresponding with
someone whose client is MIME compatible, you learn that is so "for free"

You might note that adding "MIME-Version: 1.0" to a message that is
otherwise "not MIME" (but correctly eschews the use of "non-ASCII"
characters etc), will make no difference to its interpretation.

- -- 
richard @ highwayman . com                       "Nothing seems the same
                          Still you never see the change from day to day
                                And no-one notices the customs slip away"

-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1

iQA/AwUBS0MxpZoAxkTY1oPiEQJUGQCfRqeDzYfcvXyaHt8NG7EbXvrQXAcAoLEk
XwrlvutbAIoRqe0rHNle6qp4
=+F9+
-----END PGP SIGNATURE-----