- appropriate action performed. If not found, the program search the same
- lists for "*/*" mask. If found, appropriate action performed. If not found,
- the program uses default action, which is to decode everything to text (if
- mailcap specifies a filter).
+ appropriate action is performed. If not found, the program searches the same
+ lists for "*/*" mask. If found, appropriate action is performed. If not
+ found, the program uses the default action, which is to decode everything to
+ text (if mailcap specifies a filter). This algorithm allows more specific
+ content types to override less specific: -b image/* will be processed
+ earlier than -B */*.
+</para>
+
+<para>
+ Options -e/-I/-i can also work with multipart subparts of a MIME message. In
+ case of -I/-i the entire subtree of that multipart is removed; with -i it's
+ replaced with ignore warning.
+</para>
+
+<para>
+ Initially all 5 lists are empty, so without any additional parameters
+ the program always uses the default decoding (as -t */*).
+</para>
+
+<para>
+ The 3 save options (--save-headers/body/message) are similar. They make the
+ program to save every non-multipart subpart (only headers, or body, or the
+ entire subpart: headers + body) that corresponds to the given mask to a file.
+ Before saving the message (or the subpart) is decoded according to all other
+ options and is placed to the output stream as usual. Filename for the file is
+ created using "filename" parameter from the Content-Disposition header, or
+ "name" parameter from the Content-Type header if one of those exist; a serial
+ counter is prepended to the filename to avoid collisions; if there are no
+ name/filename parameters, or the name/filename parameters contain forbidden
+ characters (null, slash, backslash) the filename is just the serial counter.
+</para>
+
+<para>
+ If the file doesn't have any extensions (no dots in the value of the
+ name/filename parameters, or the name is just the counter) the program tries
+ to guess an extension by looking up the content type in mime.types files
+ including .mime.types file in the user's home directory (if it exists). If
+ the file has an extension the program doesn't try to verify that it
+ corresponds to the content type.