.HP 5
.B mhbuild
.I file
+.RB [ \-auto " | " \-noauto ]
.RB [ \-list " | " \-nolist ]
.RB [ \-realsize " | " \-norealsize ]
.RB [ \-headers " | " \-noheaders ]
.RB [ \-contentid " | " \-nocontentid ]
.RB [ \-verbose " | " \-noverbose ]
.RB [ \-check " | " \-nocheck ]
+.RB [ \-headerencoding
+.IR encoding\-algorithm
+.RB " | " \-autoheaderencoding ]
.RB [ \-version ]
.RB [ \-help ]
.ad
.PP
.B mhbuild
creates multi-media messages as specified in RFC 2045
-to RFC 2049. Currently
-.B mhbuild
-only supports encodings in
-message bodies, and does not support the encoding of message headers as
-specified in RFC 2047.
+to RFC 2049. This includes the encoding of message headers as specified
+by RFC 2047.
.PP
If you specify the name of the composition file as \*(lq-\*(rq,
then
is not specified as above, then the character set will be labeled as
\*(lqus-ascii\*(rq.
.PP
+The
+.B \-headerencoding
+switch will indicate which algorithm to use when encoding any message headers
+that contain 8\-bit characters. The valid arguments are
+.I base64
+for based\-64 encoding and
+.I quoted
+for quoted\-printable encoding. The
+.B \-autoheaderencoding
+switch will instruct
+.B mhbuild
+to automatically pick the algorithm that results in a shorter encoded string.
+.PP
Putting this all together,
here is an example of a more complicated message draft. The
following draft will expand into a multipart/mixed message
.B mhbuild
to translate the composition file into MIME format.
.PP
+Normally it is an error to invoke
+.B mhbuild
+on file that already in MIME format. The
+.B \-auto
+switch will cause
+.B mhbuild
+to exit without error if the input file already has valid MIME headers.
+.PP
It is also possible to have the
.B whatnow
program invoke
.RB ` \-contentid '
.RB ` \-nocheck '
.RB ` \-noverbose '
+.RB ` \-autoheaderencoding '
.fi