X-Git-Url: https://diplodocus.org/git/nmh/blobdiff_plain/00d87573f5cedd2105f4e4150b1ef897e6a2310c..b0aa8cdb1c264e42d4931ca24968689c73381278:/man/mh-mime.man diff --git a/man/mh-mime.man b/man/mh-mime.man index c59896fa..ad75c8d8 100644 --- a/man/mh-mime.man +++ b/man/mh-mime.man @@ -1,4 +1,4 @@ -.TH MH\-MIME %manext7% " March 13, 2014" "%nmhversion%" +.TH MH\-MIME %manext7% "September 25, 2016" "%nmhversion%" .\" .\" %nmhwarning% .\" @@ -12,7 +12,7 @@ The acronym MIME stands for Multipurpose Internet Mail Extensions, the format of Internet messages used to send multi\-media content. The .B nmh -command suite has support for the display and composition of MIME messages, but +command suite has support for the display and composition of MIME messages, but currently MIME support is not completely integrated into all tools. This document provides an overview as to which tools support MIME message display, storage, and composition. @@ -28,30 +28,16 @@ local character set. Character set conversion will only take place if .B nmh was built with .IR iconv (3) -support. You can check the status of -.IR iconv (3) -support in -.B nmh -by executing the command -.PP -.RS 5 -.nf -mhparam\0\iconv -.fi -.RE -.PP -If it returns -.IR iconv , -then +support. See the +.IR mhparam (1) +man page for how determine whether your .B nmh -is built with +installation includes .IR iconv (3) -support. If it is blank, then -.IR iconv (3) -support is not included. +support. .PP Depending on the source and target character set, it may not be possible -to convert all characters to the local character set. In this case a +to convert all characters to the local character set. In this case a substitution character will be used for the characters that cannot be converted. .SS @@ -63,7 +49,7 @@ will automatically decode MIME-encoded headers. If you have a custom format, see the examples provided with the .B nmh distribution (found in the -.RI \*(lq %etcdir% \*(rq +.RI \*(lq %nmhetcdir% \*(rq directory) and .IR mh\-format (5) for details on how to make sure your MIME headers are properly @@ -155,8 +141,11 @@ command at the \*(lqWhat now?\*(rq prompt to process them. When replying to messages using .IR repl (1) the traditional MH method of including the original text in the reply does -not interoperate with MIME messages. As of this writing there is no -native solution for addressing this issue, but the contrib directory +not interoperate with MIME messages. The +.B \-convertargs +switch to +.IR repl (1) +provides one solution. Another solution: the contrib directory .RI ( %docdir%/contrib ) contains a Perl program called .B replyfilter @@ -166,16 +155,32 @@ to be included in a message reply. See the comments at the top of for instructions on how to configure .B nmh to work with it. +.SS +Message Rewrite +The +.IR mhfixmsg (1) +command can apply various transformations to MIME messages, including +decoding of text parts, converting the character set of text parts, +and insertion of text/plain parts to correspond to text parts of other +subtypes. +.B mhfixmsg +can also repair defects in MIME messages, such as mismatched top-level +boundary indicators and invalid Content-Transfer-Encoding values. .SH "SEE ALSO" -.IR nmh (7), -.IR mhbuild (1), .IR comp (1), +.IR iconv (3), +.IR mh\-format (5) +.IR mhbuild (1), +.IR mhfixmsg (1), +.IR mhparam (1), +.IR nmh (7), .IR repl (1), .IR whatnow (1), -.IR mh\-format (5) -.PP -.I %docdir%/contrib/replyfilter +.br +.IR %docdir%/contrib/replyfilter , +.br +.I %docdir%/contrib/replaliases .SH BUGS -MIME support should be more integrated into all of the +MIME support should be more integrated into all of the .B nmh tools than it currently is.