Removed RFC 1864 (Content-MD5) support. I.e. -check switches.

[mmh] / man / mhbuild.man1

diff --git a/man/mhbuild.man1 b/man/mhbuild.man1
index 9a78e02..babc1b2 100644 (file)
--- a/man/mhbuild.man1
+++ b/man/mhbuild.man1
@@ -16,7 +16,6 @@ mhbuild \- translate MIME composition draft
 .RB [ \-rfc934mode " | " \-norfc934mode ]
 .RB [ \-contentid " | " \-nocontentid ]
 .RB [ \-verbose " | " \-noverbose ]
-.RB [ \-check " | " \-nocheck ]
 .RB [ \-version ]
 .RB [ \-help ]
 .ad
@@ -115,14 +114,14 @@ than one line, e.g.,
 .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.
+There are four kinds of directives:
+\*(lqtype\*(rq,
+\*(lqexternal-type\*(rq,
+\*(lqmessage\*(rq (#forw),
+and \*(lqbegin\*(rq (#begin).
 .PP
-The \*(lqtype\*(rq directive is used to directly specify the type and
+.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
@@ -198,7 +197,8 @@ contents should probably be put in the file specified by the
 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
@@ -245,7 +245,8 @@ body=       command to send for retrieval
 .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
@@ -283,7 +284,8 @@ 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
-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
@@ -424,7 +426,7 @@ containing five parts:
 .RS 5
 .nf
 To: nobody@nowhere.org
-cc:
+Cc:
 Subject: Look and listen to me!
 --------
 The first part will be text/plain
@@ -438,16 +440,6 @@ This third part will be text/plain
                     /home/foobar/lib/picture.gif
 .fi
 .RE
-.SS "Integrity Check"
-If
-.B mhbuild
-is given the
-.B \-check
-switch, then it will also associate
-an integrity check with each \*(lqleaf\*(rq content.  This will add a
-Content-MD5 header field to the content, along with the md5 sum of the
-unencoded contents.  This may be used by the receiver of the message to
-verify that the contents of the message were not changed in transport.
 
 .SS "Transfer Encodings"
 After
@@ -458,16 +450,6 @@ which transfer encoding to use.  It will check for 8bit data, long lines,
 spaces at the end of lines, and clashes with multipart boundaries.  It will
 then choose a transfer encoding appropriate for each content type.
 .PP
-If an integrity check is being associated with each content by using
-the
-.B \-check
-switch, then
-.B mhbuild
-will encode each content with
-a transfer encoding, even it the content contains only 7\-bit data.  This
-is to increase the likelihood that the content is not changed while in
-transport.
-.PP
 The switch
 .B \-ebcdicsafe
 will cause
@@ -482,62 +464,18 @@ through mail gateways which involve the EBCDIC character encoding.
 .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
-.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
+is invoked by the
+.B send
+program.
+It expects an
 .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
@@ -678,7 +616,6 @@ mhlist(1), mhshow(1), mhstore(1),
 .RB ` \-realsize '
 .RB ` \-norfc934mode '
 .RB ` \-contentid '
-.RB ` \-nocheck '
 .RB ` \-noebcdicsafe '
 .RB ` \-noverbose '
 .fi