4 .TH MHLIST %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
6 mhlist \- list information about MIME messages
21 .RB [ \-headers " | " \-noheaders ]
22 .RB [ \-realsize " | " \-norealsize ]
27 .RB [ \-check " | " \-nocheck ]
34 command allows you to list information (essentially
35 a table of contents) about the various parts of a collection of
36 MIME (multi-media) messages.
39 manipulates MIME (multi-media messages) as specified
40 in RFC\-2045 thru RFC\-2049 (See
45 switch indicates that a one-line banner should be
46 displayed above the listing.
53 \*(lqnative\*(rq (decoded) format of each content prior to listing.
54 This provides an accurate count at the expense of a small delay.
58 switch is present, then the listing will show
59 any \*(lqextra\*(rq information that is present in the message,
60 such as comments in the \*(lqContent-Type\*(rq header.
68 file as the source message, rather than a message from a folder.
69 If you specify this file as \*(lq-\*(rq, then
72 accept the source message on the standard input. Note that the
73 file, or input from standard input should be a validly formatted
74 message, just like any other
78 be in mail drop format (to convert a file in mail drop format to
86 will list information about the entire
87 message (all of its parts). By using the
91 switches, you may limit the scope of this command to particular
92 subparts (of a multipart content) and/or particular content types.
94 A part specification consists of a series of numbers separated by dots.
95 For example, in a multipart content containing three parts, these
96 would be named as 1, 2, and 3, respectively. If part 2 was also a
97 multipart content containing two parts, these would be named as 2.1 and
98 2.2, respectively. Note that the
100 switch is effective for only
101 messages containing a multipart content. If a message has some other
102 kind of content, or if the part is itself another multipart content, the
104 switch will not prevent the content from being acted upon.
106 A content specification consists of a content type and a subtype.
107 The initial list of \*(lqstandard\*(rq content types and subtypes can
108 be found in RFC\-2046.
110 A list of commonly used contents is briefly reproduced here:
114 .ta \w'application 'u
118 multipart mixed, alternative, digest, parallel
119 message rfc822, partial, external-body
120 application octet-stream, postscript
127 A legal MIME message must contain a subtype specification.
129 To specify a content, regardless of its subtype, just use the
130 name of the content, e.g., \*(lqaudio\*(rq. To specify a specific
131 subtype, separate the two with a slash, e.g., \*(lqaudio/basic\*(rq.
132 Note that regardless of the values given to the
135 multipart content (of any subtype listed above) is always acted upon.
136 Further note that if the
138 switch is used, and it is desirable to
139 act on a message/external-body content, then the
142 be used twice: once for message/external-body and once for the content
143 externally referenced.
144 .SS "Checking the Contents"
149 to check each content for an
150 integrity checksum. If a content has such a checksum (specified as a
151 Content-MD5 header field), then
153 will attempt to verify the
154 integrity of the content.
159 .ta \w'%etcdir%/ExtraBigFileName 'u
160 ^$HOME/\&.mh\(ruprofile~^The user profile
163 .SH "PROFILE COMPONENTS"
167 .ta \w'ExtraBigProfileName 'u
168 ^Path:~^To determine the user's nmh directory
169 ^Current\-Folder:~^To find the default current folder
173 mhbuild(1), mhshow(1), mhstore(1), sendfiles(1)
177 .RB ` +folder "' defaults to the current folder"
178 .RB ` msgs "' defaults to cur"
188 If a folder is given, it will become the current folder. The last
189 message selected will become the current message.