Steven wrote:
The resulting file has these headers:
Content-Transfer-Encoding: binary
Content-Disposition: inline
Content-Type: text/html;
charset="UTF-8"
MIME-Version: 1.0
So if I correctly understand what I'm learning from you and Ken, this
should be compliant.
With RFC 2045, yes, but maybe not with the line length limitations of RFC 5322
§2.1.1.
I tried it just now, and the (expected) result was
mhfixmsg: Don't know how to convert /home/smw/Mail/reformatted/17352,
there is no mhfixmsg-format-text/html profile entry
...which makes sense because I don't know what to put in that profile entry.
Is there a mhfixmsg-format-text/html line in your mhn.defaults? There should
be, if you installed nmh with "make install" and one of w3m, lynx, or elinks
was already present and on your PATH.
Uh, that's a different issue. -maxunencoded 900 can cause creation of
messages with lines that long, and they wouldn't comply with RFC 5322.
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.
David
--
Nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers