X-Git-Url: https://git.phdru.name/?a=blobdiff_plain;f=mimedecode.docbook;h=8fbb51be36769d5d028d79dd3a24d959465c4c87;hb=c11b704a91997b03ad0ba624a9faf433a8e860b1;hp=746fedad5c3daaaa0a3c78c896a6f4b745e4d5f7;hpb=1d7e83e56c2d0208fd2c8e4a2d3102f339081c73;p=mimedecode.git
diff --git a/mimedecode.docbook b/mimedecode.docbook
index 746feda..8fbb51b 100644
--- a/mimedecode.docbook
+++ b/mimedecode.docbook
@@ -41,17 +41,47 @@
+
+
+
-
+
+
+
+
+
+
+
+
+
+
+
+
+
-
+
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
@@ -70,13 +100,13 @@
DESCRIPTION
Mail users, especially in non-English countries, often find that mail
-messages arrived in different formats, with different content types, in
-different encodings and charsets. Usually it is good because it allows to use
-an appropriate format/encoding/whatever. Sometimes, though, some unification is
-desirable. For example, one may want to put mail messages into an archive,
-make HTML indices, run search indexer, etc. In such situations converting
-messages to text in one character set and skipping some binary attachments is
-much desirable.
+ messages arrived in different formats, with different content types, in
+ different encodings and charsets. Usually it is good because it allows to
+ use an appropriate format/encoding/whatever. Sometimes, though, some
+ unification is desirable. For example, one may want to put mail messages
+ into an archive, make HTML indices, run search indexer, etc. In such
+ situations converting messages to text in one character set and skipping
+ some binary attachments is much desirable.
@@ -85,21 +115,23 @@ much desirable.
This is a program to decode MIME messages. The program expects one input
-file (either on command line or on stdin) which is treated as an RFC822
-message, and decodes to stdout or an output file. If the file is not an RFC822
-message it is just copied to the output one-to-one. If the file is a simple
-RFC822 message it is decoded as one part. If it is a MIME message with multiple
-parts ("attachments") all parts are decoded. Decoding can be controlled by
-command-line options.
+ file (either on command line or on stdin) which is treated as an RFC822
+ message, and decodes to stdout or an output file. If the file is not an
+ RFC822 message it is just copied to the output one-to-one. If the file is a
+ simple RFC822 message it is decoded as one part. If it is a MIME message
+ with multiple parts ("attachments") all parts are decoded. Decoding can be
+ controlled by command-line options.
- First, Subject and Content-Disposition headers are examined. If any of those
- exists, it is decoded according to RFC2047. Content-Disposition header is
- not decoded - only its "filename" parameter. Encoded header parameters
- violate the RFC, but widely deployed anyway by ignorant coders who never
- even heard about RFCs. Correct parameter encoding specified by RFC2231. This
- program decodes RFC2231-encoded parameters, too.
+ First, for every part the program removes headers and parameters listed with
+ -r and -R options. Then, Subject and Content-Disposition headers (and all
+ headers listed with -d and -p options) are examined. If any of those exists,
+ they are decoded according to RFC2047. Content-Disposition header is not
+ decoded - only its "filename" parameter. Encoded header parameters violate
+ the RFC, but widely deployed anyway by ignorant coders who never even heard
+ about RFCs. Correct parameter encoding specified by RFC2231. This program
+ decodes RFC2231-encoded parameters, too.
@@ -113,16 +145,23 @@ command-line options.
than POSIX, please don't ask me; real OS users can consult my example at
http://phdru.name/Software/dotfiles/mailcap.html).
The decoding process uses the first copiousoutput filter it can find. If
- there is no any filter the body just passed as is.
+ there are no filters the body just passed as is.
Then Content-Type header is consulted for charset. If it is not equal to the
- current locale charset the body text is recoded. Finally message headers and
- the body are flushed to stdout.
+ current locale charset and recoding is allowed the body text is recoded.
+ Finally message headers and the body are flushed to stdout.
+
+
+ Please be warned that in the following options asterisk is a shell
+ metacharacter and should be escaped or quoted. Either write -d \*,-h1,-h2
+ or -d '*,-h1,-h2' or such.
+
+OPTIONS
@@ -151,8 +190,8 @@ command-line options.
-c
- Recode different character sets in message body to current default
- charset; this is the default.
+ Recode different character sets in message bodies to the current
+ default charset; this is the default.
@@ -161,7 +200,17 @@ command-line options.
-C
- Do not recode character sets in message body.
+ Do not recode character sets in message bodies.
+
+
+
+
+
+ -f charset
+
+
+ Force this charset to be the current default charset instead of
+ the current locale.
@@ -178,21 +227,25 @@ command-line options.
- -f charset
+ -d header1[,header2,header3...]
- Force this charset to be the current default charset instead of
- the current locale.
+ Add the header(s) to a list of headers to decode; initially the
+ list contains headers "From", "To", "Cc", "Reply-To",
+ "Mail-Followup-To" and "Subject".
- -d header
+ -d *[,-header1,-header2,-header3...]
- Add the header to a list of headers to decode; initially the list
- contains headers "From" and "Subject".
+ This variant completely changes headers decoding. First, the list of
+ headers to decode is cleared. Then all the headers are decoded
+ except the given list of exceptions (headers listed with '-'). In
+ this mode it would be meaningless to give more than one -d options
+ but the program doesn't enforce it.
@@ -207,12 +260,42 @@ command-line options.
- -p header:param
+ -p header1[,header2,header3,...]:param1[,param2,param3,...]
+
+
+ Add the parameters(s) to a list of headers parameters to decode;
+ the parameters will be decoded only for the given header(s).
+ Initially the list contains header "Content-Type", parameter "name";
+ and header "Content-Disposition", parameter "filename".
+
+
+
+
+
+ -p *[,-header1,-header2,-header3,...]:param1[,param2,param3,...]
+
+
+ Add the parameters(s) to a list of headers parameters to decode;
+ the parameters will be decoded for all headers except the given
+ ones.
+
+
+
+
+
+ -p header1[,header2,header3,...]:*[,-param1,-param2,-param3,...]
+
+
+ Decode all parameters except listed for the given list of headers.
+
+
+
+
+
+ -p *[,-header1,-header2,-header3,...]:*[,-param1,-param2,-param3,...]
- Add the (header, param) pair to a list of headers' parameters to
- decode; initially the list contains header "Content-Disposition",
- parameter "filename".
+ Decode all parameters except listed for all headers (except listed).
@@ -221,7 +304,55 @@ command-line options.
-P
- Clear the list of headers' parameters to decode (make it empty).
+ Clear the list of headers parameters to decode (make it empty).
+
+
+
+
+
+ -r header1[,header2,header3...]
+
+
+ Add the header(s) to a list of headers to remove completely;
+ initially the list is empty.
+
+
+
+
+
+ -r *[,-header1,-header2,-header3...]
+
+
+ Remove all headers except listed.
+
+
+
+
+
+ -R header1[,header2,header3,...]:param1[,param2,param3,...]
+
+
+ Add the parameters(s) to a list of headers parameters to remove;
+ the parameters will be decoded only for the given header(s).
+ Initially the list is empty.
+
+
+
+
+
+ -R *[,-header1,-header2,-header3,...]:param1[,param2,param3,...]
+
+
+
+ -R header1[,header2,header3,...]:*[,-param1,-param2,-param3,...]
+
+
+
+ -R *[,-header1,-header2,-header3,...]:*[,-param1,-param2,-param3,...]
+
+
+ Remove listed parameters (or all parameters except listed) frome
+ these headers (or from all headers except listed).
@@ -283,11 +414,11 @@ cat input_file | mimedecode.py -o output_file
- The 4 list options (-beit) require more explanation. They allow a user
-to control body decoding with great flexibility. Think about said mail
-archive; for example, its maintainer wants to put there only texts, convert
-Postscript/PDF to text, pass HTML and images as is, and ignore everything
-else. Easy:
+ The 4 list options (-beit) require more explanation. They allow a user to
+ control body decoding with great flexibility. Think about said mail archive;
+ for example, its maintainer wants to put there only texts, convert
+ Postscript/PDF to text, pass HTML and images as is, and ignore everything
+ else. Easy:
@@ -298,15 +429,15 @@ else. Easy:
- When the program decodes a message (or its part), it consults
-Content-Type header. The content type is searched in all 4 lists, in order
-"text-binary-ignore-error". If found, appropriate action performed. If not
-found, the program search the same lists for "type/*" mask (the type of
-"text/html" is just "text"). If found, 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).
+ When the program decodes a message (non-MIME or a non-multipart subpart of a
+ MIME message), it consults Content-Type header. The content type is searched
+ in all 4 lists, in order "text-binary-ignore-error". If found, appropriate
+ action performed. If not found, the program search the same lists for
+ "type/*" mask (the type of "text/html" is just "text"). If found,
+ 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).
@@ -334,12 +465,13 @@ the program always uses the default decoding.
BUGS
The program may produce incorrect MIME message. The purpose of the program
-is to decode whatever it is possible to decode, not to produce absolutely
-correct MIME output. The incorrect parts are obvious - decoded Subject headers
-and filenames. Other than that output is correct MIME message. The program does
-not try to guess whether the headers are correct. For example, if a message
-header states that charset is iso8859-5, but the body is actually in utf-8
-the program will recode the message with the wrong charset.
+ is to decode whatever it is possible to decode, not to produce absolutely
+ correct MIME output. The incorrect parts are obvious - decoded
+ From/To/Cc/Reply-To/Mail-Followup-To/Subject headers and filenames. Other
+ than that output is correct MIME message. The program does not try to guess
+ whether the headers are correct. For example, if a message header states
+ that charset is iso8859-5, but the body is actually in utf-8 the program
+ will recode the message with the wrong charset.