Done: tests

[mimedecode.git] / mimedecode.docbook

diff --git a/mimedecode.docbook b/mimedecode.docbook
index f40319b6c2d96069ca2e571a215eed41a5c02226..0bfaf9c807ae783d0ce9b5ddc994a7c60aeb703a 100644 (file)
--- a/mimedecode.docbook
+++ b/mimedecode.docbook
@@ -41,6 +41,9 @@
       <arg choice="opt">
          <option>-cCDP</option>
       </arg>
+      <arg choice="opt">
+         <option>-H|--host=hostname</option>
+      </arg>
       <arg choice="opt">
          <option>-f charset</option>
       </arg>
@@ -163,6 +166,17 @@ flushed to stdout.
       </listitem>
    </varlistentry>
 
+   <varlistentry>
+      <term>-H hostname</term>
+      <term>--host=hostname</term>
+      <listitem>
+         <para>
+           Use this hostname in X-MIME-Autoconverted headers instead of the
+           current hostname.
+         </para>
+      </listitem>
+   </varlistentry>
+
    <varlistentry>
       <term>-f charset</term>
       <listitem>
@@ -325,7 +339,7 @@ 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 koi8-r -
-the program will recode the message to the wrong charset.
+the program will recode the message with the wrong charset.
 </para>
 </refsect1>