Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: Mime-Version and no Content-Type
Date: 17 Dec 1998 05:27:02 -0800	[thread overview]
Message-ID: <m37lvqj3vd.fsf@reader.newsguy.com> (raw)
In-Reply-To: Hrvoje Niksic's message of "16 Dec 1998 17:39:18 +0100"

Hrvoje Niksic <hniksic@srce.hr> writes:

Looking at Hrvoje's message brings to mind a somewhat related, but very minor
nitpick.   A friend helping me get mail working properly on a
laptop I'm using,  noticed my "MIME" header and commented that this is
normally in uppercase as shown in Hrvoje's quotes:

>    Default RFC 822 messages without a MIME Content-Type header are taken

>    the presence of a MIME-Version header field and the absence of any

 My setup always shows the mime header like so:

Mime-Version: 1.0

Is this something that is normally set locally?  Or is there anything
to the idea that it should be in upper-case?

-- 
Harry Putnam <reader@newsguy.com>
Running Redhat Linux 5.1


  parent reply	other threads:[~1998-12-17 13:27 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 [this message]
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
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=m37lvqj3vd.fsf@reader.newsguy.com \
    --to=reader@newsguy.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).