.HP 5
.B mhbuild
.I file
-.RB [ \-list " | " \-nolist ]
-.RB [ \-headers " | " \-noheaders ]
-.RB [ \-rfc934mode " | " \-norfc934mode ]
-.RB [ \-contentid " | " \-nocontentid ]
.RB [ \-verbose " | " \-noverbose ]
-.RB [ \-version ]
+.RB [ \-Version ]
.RB [ \-help ]
.ad
.SH DESCRIPTION
recover the
.B mhbuild
input file.
-.SS "Listing the Contents"
-The
-.B \-list
-switch tells
-.B mhbuild
-to list the table of contents associated with the MIME message that is created.
-.PP
-The
-.B \-headers
-switch indicates
-that a one-line banner should be displayed above the listing.
-The size of the \*(lqnative\*(rq
-(decoded) format of each content is evaluated. This provides an
-accurate count at the expense of a small delay.
-If the
-.B \-verbose
-switch
-is present, then the listing will show any \*(lqextra\*(rq information
-that is present in the message, such as comments in the
-\*(lqContent-Type\*(rq header.
.SS "Translating the Composition File"
.B mhbuild
is essentially a filter to aid in the composition of MIME
group of messages to include. You may optionally specify the name of
the folder and which messages are to be forwarded. If a folder is not
given, it defaults to the current folder. Similarly, if a message is not
-given, it defaults to the current message. Hence, the message directive
-is similar to the
-.B forw
-command, except that the former uses
-the MIME rules for encapsulation rather than those specified in RFC\-934.
+given, it defaults to the current message. The message directive
+is used by
+.BR forw .
+.PP
For example,
.PP
.RS 5
will add a content of type \*(lqmultipart/digest\*(rq
and include each message as a subpart of this content.
.PP
-If you are using this directive to include more than one message, you
-may use the
-.B \-rfc934mode
-switch. This switch will indicate that
-.B mhbuild
-should attempt to utilize the MIME encapsulation rules
-in such a way that the \*(lqmultipart/digest\*(rq that is created
-is (mostly) compatible with the encapsulation specified in RFC\-934.
-If given, then RFC\-934 compliant user-agents should be able to burst the
-message on reception\0--\0providing that the messages being encapsulated
-do not contain encapsulated messages themselves. The drawback of this
-approach is that the encapsulations are generated by placing an extra
-newline at the end of the body of each message.
-.PP
.B "(3) The \*(lqbegin\*(rq directive
is used to create a multipart content.
When using the \*(lqbegin\*(rq directive, you must specify at least one
will generate a unique \*(lqContent-ID:\*(rq for each directive,
corresponding to each message part; however, the user may override
this by defining the ID using the \*(lq<\*(rq and \*(lq>\*(rq
-characters. The
-.B \-nocontentid
-switch suppresses creation of all \*(lqContent-ID:\*(rq headers,
-even in the top level of the message.
+characters.
.PP
In addition to the various directives, plaintext can be present.
Plaintext is gathered, until a directive is found or the draft is
.fi
.SH "SEE ALSO"
-mhlist(1), show(1), mhstore(1),
-.br
-.I "Proposed Standard for Message Encapsulation"
-(RFC\-934),
+mhlist(1), show(1), mhstore(1), forw(1),
.br
.I "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"
(RFC\-2045),
.SH DEFAULTS
.nf
-.RB ` \-headers '
-.RB ` \-norfc934mode '
-.RB ` \-contentid '
.RB ` \-noverbose '
.fi
.SH CONTEXT
If a folder is given, it will become the current folder. The last
message selected will become the current message.
+
+.SH BUGS
+Outlook 2002 won't display attachments that have a Content-ID header.
+This is a bug in Outlook 2002, not in
+.BR mhbuild .
+To workaround it, invoke \fIe mhbuild\fP manually at the Whatnow prompt
+and edit the draft again thereafter, removing the Content-ID headers.
+Then send it.
+There used to be a
+.B \-nocontentid
+switch to prevent Content-ID headers to be inserted, but as it was considerd
+wrong to complicate all other MUAs instead of forcing the developers and users
+of broken MUAs to fix or change their software, it was removed.
projects / mmh / blobdiff