X-Git-Url: https://git.phdru.name/?p=mimedecode.git;a=blobdiff_plain;f=mimedecode.docbook;h=064729fd507b5a067c187911ef61460bd945c2e0;hp=db1bbfafedc742c0c905d125d9dc64d48873c749;hb=e523d0dbf7c78b7a66a72b8b3b13e7bf3ce3ec5b;hpb=2c5be6f201a2d0bc67356a5b114071139050c135

diff --git a/mimedecode.docbook b/mimedecode.docbook
index db1bbfa..064729f 100644
--- a/mimedecode.docbook
+++ b/mimedecode.docbook
@@ -192,7 +192,7 @@ command-line options.
       <listitem>
          <para>
             Add the header to a list of headers to decode; initially the list
-            contains headers "From", "To", "Cc" and "Subject".
+            contains headers "From", "To", "Cc", "Reply-To" and "Subject".
          </para>
       </listitem>
    </varlistentry>
@@ -337,11 +337,11 @@ the program always uses the default decoding.
    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
-   From/To/Cc/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.
+   From/To/Cc/Reply-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.
 </para>
 </refsect1>