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

[mmh] / man / mhstore.man1

diff --git a/man/mhstore.man1 b/man/mhstore.man1
index ddb43f8..0a338e7 100644 (file)
--- a/man/mhstore.man1
+++ b/man/mhstore.man1
@@ -19,12 +19,10 @@ mhstore \- store contents of MIME messages into files
 .IR content ]
 \&...
 .RB [ \-auto " | " \-noauto ]
-.RB [ \-verbose " | " \-noverbose ]
 .RB [ \-rcache
 .IR policy ]
 .RB [ \-wcache
 .IR policy ]
-.RB [ \-check " | " \-nocheck ]
 .RB [ \-version ]
 .RB [ \-help ]
 .ad
@@ -125,17 +123,6 @@ desirable to act on a message/external-body content, then the
 .B \-type
 switch must be used twice: once for message/external-body
 and once for the content externally referenced.
-.SS "Checking the Contents"
-The
-.B \-check
-switch tells
-.B mhstore
-to check each content for
-an integrity checksum.  If a content has such a checksum (specified
-as a Content-MD5 header field), then
-.B mhstore
-will attempt to
-verify the integrity of the content.
 .SS "Storing the Contents"
 The
 .B mhstore
@@ -219,7 +206,9 @@ to store the content.  If the formatting string starts with a '/',
 then the content will be stored in the full path given, else the
 file name will be relative to the value of \*(lqnmh-storage\*(rq or
 the current working directory.  Any escapes (given below) will be
-expanded, except for the a-escape.
+expanded, except for the a-escape.  Note that if \*(lqnmh-storage\*(rq
+is not an absolute path, it will be relative to the folder that
+contains the message(s).
 .PP
 A command or pathname formatting string may contain the following
 escapes.  If the content isn't part of a multipart (of any subtype
@@ -293,7 +282,7 @@ message in the following fashion:
    8       message/partial           18K part 4 of 4
 % mhstore 5-8
 reassembling partials 5,6,7,8 to folder inbox as message 9
-% mhlist -verbose 9
+% mhlist 9
  msg part  type/subtype             size description
    9       application/octet-stream 118K
              (extract with uncompress | tar xvpf -)
@@ -312,6 +301,48 @@ are combined in the correct order.  But if
 can not
 locate every partial necessary to reassemble the message, it will
 not store anything.
+RE
+.PP
+By using the
+.B \-auto
+switch,
+.B mhstore
+will automatically do the extraction for you:
+.PP
+.RS 5
+.nf
+% mhlist 5-8
+ msg part  type/subtype             size description
+   5       message/partial           47K part 1 of 4
+   6       message/partial           47K part 2 of 4
+   7       message/partial           47K part 3 of 4
+   8       message/partial           18K part 4 of 4
+% mhstore 5-8
+reassembling partials 5,6,7,8 to folder inbox as message 9
+% mhlist 9
+ msg part  type/subtype             size description
+   9       application/octet-stream 118K
+             (extract with uncompress | tar xvpf -)
+             type=tar
+             conversions=compress
+% mhstore -auto 9
+-- tar listing appears here as files are extracted
+.fi
+.RE
+.PP
+As the second
+.B tar
+listing is generated, the files are extracted.
+A prudent user will never put
+.B \-auto
+in the profile.
+The correct procedure is to first use
+.B mhlist
+to find out what will be extracted.  Then
+.B mhstore
+can be invoked with
+.B \-auto
+to perform the extraction.
 .SS "External Access"
 For contents of type message/external-body,
 \fImhstore\fR supports these access-types:
@@ -461,10 +492,8 @@ mhbuild(1), mhlist(1), mhshow(1), sendfiles(1)
 .RB ` +folder "' defaults to the current folder"
 .RB ` msgs "' defaults to cur"
 .RB ` \-noauto '
-.RB ` \-nocheck '
-.RB ` \-rcache ask '
-.RB ` \-wcache ask '
-.RB ` \-noverbose '
+.RB ` \-rcache \ ask'
+.RB ` \-wcache \ ask'
 
 .SH CONTEXT
 If a folder is given, it will become the current folder.  The last