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