Re: Mime-Version and no Content-Type

[Hrvoje Niksic <hniksic@srce.hr>]

Dale Hagglund <rdh@best.com> writes:

> > Yes, but the very same RFC explicitly states that all header names
> > are case-insensitive.
> 
> Oh come on, who reads documentation?

Anyone who wants their mail reader *not* to be totally broken.  Has
anyone provided a specific example of a mail reader known to be broken 
that way?

> Isn't the real concern here providing for broken mail readers that
> have been programmed ``by example''.

The example is provided by the very documentation you claim noone to
read.

Please get my point right here: I *prefer* `MIME-Version' to
`Mime-Version'; I've even sent out a patch that changes what
message.el emits, but I want things named correctly.  Emitting
MIME-Version vs. emitting Mime-Version is aesthetics.  Parsing
MIME-Version but not parsing Mime-Version is brokenness.

If there is a mailer that parses internet headers case-sensitively, it 
will break before it goes out of the house.

> The *safest* thing to do is probably to use the capitalization shown
> in the MIME RFCs in outgoing messages.  I don't think the aesthetics
> of it are all that relevant,

Of course it is; aestheics is the reason why that particular case was
used in the RFCs.