.fi
.RE
.PP
-There are four kinds of directives: \*(lqtype\*(rq directives, which
-name the type and subtype of the content; \*(lqexternal-type\*(rq
-directives, which also name the type and subtype of the content; the
-\*(lqmessage\*(rq directive (#forw), which is used to forward one or
-more messages; and, the \*(lqbegin\*(rq directive (#begin), which is
-used to create a multipart content.
-.PP
-The \*(lqtype\*(rq directive is used to directly specify the type and
+There are four kinds of directives:
+\*(lqtype\*(rq,
+\*(lqexternal-type\*(rq,
+\*(lqmessage\*(rq (#forw),
+and \*(lqbegin\*(rq (#begin).
+.PP
+.B "(1) The \*(lqtype\*(rq directive
+is used to directly specify the type and
subtype of a content. You may only specify discrete types in this manner
(can't specify the types multipart or message with this directive).
You may optionally specify the name of a file containing the contents
environment variable, instead of directly in your
user profile.
.PP
-The \*(lqexternal-type\*(rq directives are used to provide a MIME
+.B "(2) The \*(lqexternal-type\*(rq directives
+are used to provide a MIME
reference to a content, rather than enclosing the contents itself
(for instance, by specifying an ftp site). Hence, instead of
providing a filename as with the type directives, external-parameters
.fi
.RE
.PP
-The \*(lqmessage\*(rq directive (#forw) is used to specify a message or
+.B "(3) The \*(lqmessage\*(rq directive (#forw)
+is used to specify a message or
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
approach is that the encapsulations are generated by placing an extra
newline at the end of the body of each message.
.PP
-The \*(lqbegin\*(rq directive is used to create a multipart content.
+.B "(4) The \*(lqbegin\*(rq directive
+is used to create a multipart content.
When using the \*(lqbegin\*(rq directive, you must specify at least one
content between the begin and end pairs.
.PP
.RS 5
.nf
To: nobody@nowhere.org
-cc:
+Cc:
Subject: Look and listen to me!
--------
The first part will be text/plain
.SS "Invoking mhbuild"
Typically,
.B mhbuild
- is invoked by the
-.B whatnow
-program. This
-command will expect the body of the draft to be formatted as an
+is invoked by the
+.B send
+program.
+It expects an
.B mhbuild
-composition file. Once you have composed this input file
-using a command such as
-.BR comp ,
-.BR repl ,
-or
-.BR forw ,
-you invoke
-.B mhbuild
-at the \*(lqWhat now\*(rq prompt with
-.PP
-.RS 5
-What now? mime
-.RE
-.PP
-prior to sending the draft. This will cause
-.B whatnow
-to execute
-.B mhbuild
-to translate the composition file into MIME format.
-.PP
-It is also possible to have the
-.B whatnow
-program invoke
-.B mhbuild
-automatically when a message is sent. To do this, you must add the line
-.PP
-.RS 5
-automimeproc: 1
-.RE
-.PP
-to your
-.I .mmh/profile
-file.
-.PP
-Finally, you should consider adding this line to your profile:
-.PP
-.RS 5
-lproc: show
-.RE
-.PP
-This way, if you decide to
-.B list
-after invoking
-.BR mime ,
-the command
-.PP
-.RS 5
-What now? list
-.RE
+composition file, which
+.B send
+will create, from the draft file, if MIME features are requested.
+This is the case with attachment headers.
.PP
-will work as you expect.
+In contrast to previous versions, the user does not need to care
+for any special actions anymore.
.SS "User Environment"
Because the environment in which