[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: DuaneTime
Subject: [nmh-workers] Can't forward MIME-encoded message
Date: Thu, 09 May 2019 02:34:20 +0000

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

For instance, if the message header contains

Content-Type: multipart/alternative;

and the body of the message contains

Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

nmh will completely remove the "Content-Type" in the header, so that the 
message is just garbage and cannot be read.  (It leaves the two "Parts" in the 
body though.)

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.

My nmh release came with Debian version 9.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]