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

[Ken Hornstein]

>After upgrading to nmh v1.6, I can no longer forward a message with a
>content-type header.

When you say, "Forward", what _EXACTLY_ do you mean?

I just 3 different things with the latest nmh, and they all behaved
"as designed".

- When I forwarded a message with forw -mime, it generates a new message
  with an message/rfc822 MIME type; the original message contained
  in the message/rfc822 has the correct Content-Type header

- I forwared a message with forw -nomime; that message just contained the
  complete text of the message in the body, so the mail reader didn't
  interpret it as MIME, but it's always done that; AFAICT that has never
  changed.

- I used dist; the redistributed message contained all of the correct MIME
  headers, including Content-Type.

So it's not that I don't believe you, but I cannot reproduce what you
are describing; if you could explain what exactly you are doing, that
would be helpful.

>I suspect this is the result of "mhbuild" now being unconditionally
>inflicted on the message, but I can't find any way to disable it, in
>order to test that.

When run from send(1), mhbuild is being invoked with the "-auto" flag,
which will exit silently if it sees a Mime-Version or
Content-Transfer-Encoding header; that is done specifically so mhbuild
doesn't affect existing MIME headers.  So that shouldn't affect anything.
But if you really want to disable that, you can control that via the
buildmimeproc profile entry (see mh-profile(1)); set it to /bin/true
or whatever.

--Ken