Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Mime-Version and no Content-Type
Date: 17 Dec 1998 18:22:59 +0100	[thread overview]
Message-ID: <m3ogp2vg24.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Steinar Bang's message of "16 Dec 1998 18:44:21 +0100"

Steinar Bang <sb@metis.no> writes:

> Nowhere in the 2045 quote above _recommends_ that headers are left
> out.  At least nowhere I can see.  The quote only describes what
> *should* happen if the headers aren't there.

Yup.  Does RFC2045 (or any of the following) say anything at all about 
adding headers that express default values, and whether that is nice
or not?  I can't find anything...

Anyway, we live in the real world, and since not adding the CT and CTE
header breaks other people's stupid software, I think Gnus should
always add CT and CTE.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


  reply	other threads:[~1998-12-17 17:22 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 [this message]
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
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=m3ogp2vg24.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    /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).