Steven wrote:
but it sounds like you're suggesting that
the entry in /local/pkg/nmh/root-nmh-1.7/etc/mhn.defaults should be picked
up directory from there, and that isn't happening.
Right. Does the full path to mhn.defaults shown by "man mhfixmsg" match
/local/pkg/nmh/root-nmh-1.7/etc/mhn.defaults ? If it does, maybe run
mhfixmsg under ltrace or something similar to see exactly what file it's
trying to open.
I thought Ken said the RFC 5322 limit was 998. But...
Right. He also noted that he's had problems with insertion of '!' in long
lines of HTML.
What about the idea of reformatting the text/html part to reduce the line
width?
Then -maxunencoded wouldn't be necessary. Though I'm not sure if you're
talking about outgoing or incoming messages here.
I've been playing with tidy (AKA html-tidy), and it's capable of
transforming the HTML message I received last week from a single line of
42187 characters into a version with 1896 lines with a maximum line width
of 138.
Is there a way to get mhfixmsg to decode the base64 and then run it through
tidy with a given set of command-line options?
Yes, via mhfixmsg-format-text/html. See the mhfixmsg and mhshow man pages.
David
--
Nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers