Re: [nmh-workers] Can't forward MIME-encoded message

[Ken Hornstein]

>The only *mandatory* header for "forwarding" (yeah, right) a
>pre-existing message is "Content-type", since it has the (pre-generated)
>"Boundary" flag...  So I just edit everything else out.

This is the problem, here, because that is NOT true.

A MIME message needs a MIME-Version header, full stop, no exceptions;
this is unambiguous (see RFC 2045, §4).  This is what we trigger on to
make mhbuild do the right thing.  If we don't see a MIME-Version header,
we go on the assumption that the existing draft is NOT a MIME message,
and we MIME-ify the resulting draft, which I suspect ends up generating
a new Content-Type header for your message which does not contain a
boundary marker (because the message isn't a MIME message according to
the rules).

So, I have to say that I don't see this as a nmh bug ... if you want
to feed a MIME message into mhbuild you should include a MIME-Version
header; it's not meaningless at all.  If you are trying to send out a
message that does not contain a MIME-Version header, then that is not
valid according to the standards.

--Ken