Comment 12 for bug 265930

Originator: NO

Thanks for the response, msapiro. marc.info's raw copy of it looks
basically identical to the version of that message that arrived in my
inbox, so i'd say it's a correct copy. The RFC822 headers for the raw
message were:

Return-Path: <email address hidden>
To: <email address hidden>
Subject: Re: scp -t . - possible idea for additional parameter
From: Daniel Kahn Gillmor <email address hidden>
Date: Thu, 11 Oct 2007 12:34:23 -0400
Message-ID: <email address hidden>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1431543891=="

When i supply the concatenation of those headers, a blank line, and then
the raw message to msglint, the IETF's message validator [0], it outputs:

-----------
OK: found part multipart/mixed line 10
OK: preamble 10:
OK: found part multipart/signed line 15
OK: preamble 15:
OK: found default part text/plain line 18
OK: found part application/pgp-signature line 67
OK: epilogue 86:
WARNING: MIME headers should only be 'Content-*'. No meaning will apply to

         header 'MIME-Version' at line 89
OK: found part text/plain line 93
-----------

So that validator doesn't have any problem with the message (it assumes
the part starting at line 18, which is the section you're suggesting is
invalid, is text/plain). Is the validator wrong in assuming that? I don't
know the relevant specifications well enough to tell myself. Can you show
me where it's a requirement that each MIME section have a content-type?

Thanks for looking into this.

[0] http://www.apps.ietf.org/msglint.html