[EAI] MIME-Version: and RFC 2049 (Re: MIME questions (was: draft-hurtta-eai-messagestore-00.txt))

[Kari Hurtta <hurtta+gmane at siilo.fmi.fi>]

Frank Ellermann <nobody at xyzzy.claranet.de> writes
in gmane.ietf.ima:

<...>
> > Label
> >   MIME-Version: 2.0
> > may be usefull to indicate that downgrade is
> > required also for header fields on MIME
> > structure.
> 
> Yes, and it would warn old MIME parsers that
> they might stumble over some surprises (in the
> form of raw UTF-8) if they try to parse "2.0"
> as "1.0".  We could also formally require 2231
> support for MIME-Version 2.0, just to be sure.

It is unlikely that MIME-Version header field is checked.


RFC 2049: Multipurpose Internet Mail Extensions
                  (MIME) Part Five:
             Conformance Criteria and Examples

--------clip---------------clap---------------------------------
    (1)   Always generate a "MIME-Version: 1.0" header field in
          any message it creates.

    (2)   Recognize the Content-Transfer-Encoding header field
          and decode all received data encoded by either quoted-
          printable or base64 implementations.  The identity
          transformations 7bit, 8bit, and binary must also be
          recognized.

<...>

    (13)  The following sentence has been removed from the
          discussion of the MIME-Version header: "However,
          conformant software is encouraged to check the version
          number and at least warn the user if an unrecognized
          MIME-version is encountered."

--------clip---------------clap---------------------------------

It is quite clear, that MIME-Version: header field is 
expeted to be ignored !


(My MUA checks MIME-Version: header field, and perhaps
 do not be MIME-conformant ... :-) )

/ Kari Hurtta


_______________________________________________
IMA mailing list
IMA at ietf.org
https://www1.ietf.org/mailman/listinfo/ima