]> granicus.if.org Git - neomutt/commitdiff
Mention self_encrypt options in the documentation. (closes #3983)
authorKevin McCarthy <kevin@8t8.us>
Thu, 28 Dec 2017 21:07:21 +0000 (13:07 -0800)
committerRichard Russon <rich@flatcap.org>
Fri, 5 Jan 2018 00:43:41 +0000 (00:43 +0000)
Add a paragraph to the "Sending Cryptographically Signed/Encrypted
Messages" section of the manual.

doc/manual.xml.head

index c597b90613b0cea7d3e87fdb1614bd7a9569f131..7c688764fcbe6f55300a43a391c7c5a38b71a656 100644 (file)
@@ -2706,6 +2706,13 @@ color sidebar_divider   color8  default
         <para>Once you have successfully finished the key selection, the
         message will be encrypted using the selected public keys when sent
         out.</para>
+       <para>
+       To ensure you can view encrypted message you have sent, you
+       may wish to set <link linkend="pgp-self-encrypt">$pgp_self_encrypt</link>
+       and <link linkend="pgp-self-encrypt-as">$pgp_self_encrypt_as</link> for PGP, or
+       <link linkend="smime-self-encrypt">$smime_self_encrypt</link>
+       and <link linkend="smime-self-encrypt-as">$smime_self_encrypt_as</link> for S/MIME.
+       </para>
         <para>Most fields of the entries in the key selection menu (see also
         <link linkend="pgp-entry-format">$pgp_entry_format</link>) have obvious
         meanings. But some explanations on the capabilities, flags, and