[Top][All Lists]

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

Re: [Nmh-workers] Starting the final call for features for 1.7

From: Ken Hornstein
Subject: Re: [Nmh-workers] Starting the final call for features for 1.7
Date: Sat, 24 Sep 2016 10:41:18 -0400

>My nmh displays base-64 encoded mail just fine, but if you try to reply
>or forward with the message quoted, it doesn't convert.  I get a base-64
>encoded mail about once every 5 years, so it hasn't been worth complaining
>about, and for all I know you have already fixed this.  But I thought it
>was worth mentioning.

Wow, ONLY once every 5 years??  I get those like a few times a day!  Well,
that also includes email with quoted-printable and having a few weird

David already pointed you toward replfilter; that's been around for a
while (since 1.5) and I thought it was well known, but still people
don't know about it.  Like most of the MIME support in nmh, it's kind of
bolted on, but it does make MIME replies reasonable.

For FORWARDING mime email, well, that's actually been possible for a while.
You have two options: you can use dist(1), which some people find confusing
when they receive a message used by it (the whole message ends up intact,
and the sender appears in the "Resent-From" header), or forw -mime, which
generates a mhbuild directive so you have to make sure you "mime" the
message at the What now? prompt.  That makes the forwarded message into
a message/rfc822 MIME part, and all of the MIME structure of the enclosed
message is preserved.

In a future release I am hoping that by default repl(1) will be much smarter
than it is now.  That's a much harder job that it appears.


reply via email to

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