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 ]
28 .RB [ \-verbose " | " \-noverbose ]
35 command allows you to list information (essentially
36 a table of contents) about the various parts of a collection of
37 MIME (multi-media) messages.
40 manipulates MIME (multi-media messages) as specified
41 in RFC\-2045 thru RFC\-2049 (See
46 switch indicates that a one-line banner should be
47 displayed above the listing.
54 \*(lqnative\*(rq (decoded) format of each content prior to listing.
55 This provides an accurate count at the expense of a small delay.
59 switch is present, then the listing will show
60 any \*(lqextra\*(rq information that is present in the message,
61 such as comments in the \*(lqContent-Type\*(rq header.
69 file as the source message, rather than a message from a folder.
70 If you specify this file as \*(lq-\*(rq, then
73 accept the source message on the standard input. Note that the
74 file, or input from standard input should be a validly formatted
75 message, just like any other
79 be in mail drop format (to convert a file in mail drop format to
87 will list information about the entire
88 message (all of its parts). By using the
92 switches, you may limit the scope of this command to particular
93 subparts (of a multipart content) and/or particular content types.
95 A part specification consists of a series of numbers separated by dots.
96 For example, in a multipart content containing three parts, these
97 would be named as 1, 2, and 3, respectively. If part 2 was also a
98 multipart content containing two parts, these would be named as 2.1 and
99 2.2, respectively. Note that the
101 switch is effective for only
102 messages containing a multipart content. If a message has some other
103 kind of content, or if the part is itself another multipart content, the
105 switch will not prevent the content from being acted upon.
107 A content specification consists of a content type and a subtype.
108 The initial list of \*(lqstandard\*(rq content types and subtypes can
109 be found in RFC\-2046.
111 A list of commonly used contents is briefly reproduced here:
115 .ta \w'application 'u
119 multipart mixed, alternative, digest, parallel
120 message rfc822, partial, external-body
121 application octet-stream, postscript
128 A legal MIME message must contain a subtype specification.
130 To specify a content, regardless of its subtype, just use the
131 name of the content, e.g., \*(lqaudio\*(rq. To specify a specific
132 subtype, separate the two with a slash, e.g., \*(lqaudio/basic\*(rq.
133 Note that regardless of the values given to the
136 multipart content (of any subtype listed above) is always acted upon.
137 Further note that if the
139 switch is used, and it is desirable to
140 act on a message/external-body content, then the
143 be used twice: once for message/external-body and once for the content
144 externally referenced.
145 .SS "Checking the Contents"
150 to check each content for an
151 integrity checksum. If a content has such a checksum (specified as a
152 Content-MD5 header field), then
154 will attempt to verify the
155 integrity of the content.
160 .ta \w'%etcdir%/ExtraBigFileName 'u
161 ^$HOME/\&.mh\(ruprofile~^The user profile
164 .SH "PROFILE COMPONENTS"
168 .ta \w'ExtraBigProfileName 'u
169 ^Path:~^To determine the user's nmh directory
170 ^Current\-Folder:~^To find the default current folder
174 mhbuild(1), mhshow(1), mhstore(1), sendfiles(1)
178 .RB ` +folder "' defaults to the current folder"
179 .RB ` msgs "' defaults to cur"
183 .RB ` \-rcache\ ask '
184 .RB ` \-wcache\ ask '
189 If a folder is given, it will become the current folder. The last
190 message selected will become the current message.