From: Dale Hagglund <rdh@best.com>
Subject: Re: Mime-Version and no Content-Type
Date: 19 Dec 1998 11:12:48 -0800 [thread overview]
Message-ID: <86pv9grln3.fsf@ponoka.battleriver.com> (raw)
In-Reply-To: Hrvoje Niksic's message of "19 Dec 1998 14:02:42 +0100"
Hrvoje Niksic <hniksic@srce.hr> writes:
> François Pinard <pinard@iro.umontreal.ca> writes:
>
> > For one, when I had to generate such headers, I used `MIME-Version'
> > not by personal taste, but because it was written this way in the
> > MIME RFC's (if I remember correctly :-).
>
> Yes, but the very same RFC explicitly states that all header names are
> case-insensitive.
Oh come on, who reads documentation? Isn't the real concern here
providing for broken mail readers that have been programmed ``by
example''.
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, since gnus doesn't normally show us the
MIME-Version (or Mime-Version, or mImE-vErSiOn, or whatever) header
anyway.
Dale.
next prev parent reply other threads:[~1998-12-19 19:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-16 13:40 Lars Magne Ingebrigtsen
1998-12-16 14:04 ` Karl Kleinpaste
1998-12-16 16:30 ` Steinar Bang
1998-12-16 16:39 ` Hrvoje Niksic
1998-12-16 17:44 ` Steinar Bang
1998-12-17 17:22 ` Lars Magne Ingebrigtsen
1998-12-17 13:27 ` Harry Putnam
1998-12-17 14:04 ` Colin Rafferty
1998-12-17 14:40 ` Harry Putnam
1998-12-17 17:20 ` Lars Magne Ingebrigtsen
1998-12-18 3:35 ` Harry Putnam
1998-12-18 3:41 ` Hrvoje Niksic
1998-12-17 14:34 ` Hrvoje Niksic
1998-12-17 15:44 ` François Pinard
1998-12-19 13:02 ` Hrvoje Niksic
1998-12-19 19:12 ` Dale Hagglund [this message]
1998-12-19 19:30 ` Hrvoje Niksic
1998-12-19 22:12 ` Lars Magne Ingebrigtsen
1998-12-16 15:03 ` Hrvoje Niksic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86pv9grln3.fsf@ponoka.battleriver.com \
--to=rdh@best.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).