Gnus development mailing list
 help / color / mirror / Atom feed
From: Jacob Morzinski <jmorzins@MIT.EDU>
Cc: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: digests and MIME
Date: 21 Nov 1996 01:58:46 -0500	[thread overview]
Message-ID: <w6mwwvgexy1.fsf@w20-575-83.MIT.EDU> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 21 Nov 1996 03:29:03 +0100

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> For all I know, it may be my screwed-up sendmail config that messes
> things up...  No, wait, it can't be, because my machine doesn't touch
> mail that goes through ifi.  Let's see...  The sendmail at ifi *will*
> encode things that "need" encoding, unless there already is a
> "Mime-version: 1.0" header in there.  Perhaps it doesn't like those
> "Mime-Version: 1.0 (generated by tm-edit 7.94)" headers?  Does the
> MIME standard allow that?


My reading of the RFC's suggests that it does allow it.  Here is an
excerpt from RFC 1521, which seems to be the one that applies in this
case:

[begin excerpt]

   Therefore, this document defines a new header field, "MIME-Version",
   which is to be used to declare the version of the Internet message
   body format standard in use.

   Messages composed in accordance with this document MUST include such
   a header field, with the following verbatim text:

   MIME-Version: 1.0

   The presence of this header field is an assertion that the message
   has been composed in compliance with this document.

   Since it is possible that a future document might extend the message
   format standard again, a formal BNF is given for the content of the
   MIME-Version field:

   version := "MIME-Version" ":" 1*DIGIT "." 1*DIGIT

[..snip..]

   NOTE TO IMPLEMENTORS: All header fields defined in this document,
   including MIME-Version, Content-type, etc., are subject to the
   general syntactic rules for header fields specified in RFC 822.  In
   particular, all can include comments, which means that the following
   two MIME-Version fields are equivalent:

                    MIME-Version: 1.0
                    MIME-Version: 1.0 (Generated by GBD-killer 3.7)

[end excerpt]


The Mime-version field was first defined in RFC 1341.  I didn't find
any more recent RFC's, overriding the header definition given here.

(Of couse, the sendmail at ifi might not have been taught to ignore
comments in the Mime-version header.)

-- 
 Jacob Morzinski                                jmorzins@mit.edu


  reply	other threads:[~1996-11-21  6:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-11-20 14:43 Colin Rafferty
1996-11-20 18:20 ` Steven L Baur
1996-11-20 20:45   ` Colin Rafferty
1996-11-20 21:34     ` Lars Magne Ingebrigtsen
1996-11-20 23:00       ` Colin Rafferty
1996-11-21  2:26         ` Lars Magne Ingebrigtsen
1996-11-21  5:02         ` Steven L Baur
1996-11-21  5:49           ` Hrvoje Niksic
1996-11-20 22:45     ` Steven L Baur
1996-11-20 23:13       ` Colin Rafferty
1996-11-21  0:15         ` Steven L Baur
1996-11-21  2:29           ` Lars Magne Ingebrigtsen
1996-11-21  6:58             ` Jacob Morzinski [this message]
1996-11-21 15:58       ` François Pinard
1996-11-21 16:29         ` Lars Magne Ingebrigtsen
1996-11-21 18:20           ` Steven L Baur
1996-11-21 19:39             ` Lars Magne Ingebrigtsen

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=w6mwwvgexy1.fsf@w20-575-83.MIT.EDU \
    --to=jmorzins@mit.edu \
    --cc=larsi@ifi.uio.no \
    /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).