[Top][All Lists]

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

Re: [Nmh-workers] Unexpected munging of outgoing message with nmh 1.6

From: David Levine
Subject: Re: [Nmh-workers] Unexpected munging of outgoing message with nmh 1.6
Date: Mon, 07 Nov 2016 13:35:37 -0500

Tom wrote:

> Ordinarily, and in every previous version of nmh, that would have
> been transmitted as-is.  But today, something decided that it needed
> to be transmitted as quoted-printable, and that seems to have included
> a decision that backslash-newline sequences should be deleted.

Really?  I just tried a quick test, and a backslash-newline was
preserved.  Can you provide a small example?

And while I'm not a fan of quoted-printable, it (or another encoding)
is required in some cases (see below).  mhstore(1) can be used to
extract the decoded content.  Does it?

> Why would some purely ASCII text get converted to quoted-printable?

    It [mhbuild(1)] will check for 8bit data, long lines, spaces
    at the end of lines, and clashes with multipart boundaries.

The default max line length to avoid encoding is 78, but can be
overridden with the -maxunencoded switch to mhbuild.  Note that
lines must be limited to 998 characters to comply with RFC 5322
Sec. 2.1.1.

> And how can I prevent it from changing the contents of the text
> when it does that?

I would start with mhbuild (mime at the What now? prompt)
-maxunen 998, which you can add to your profile, of course.


reply via email to

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