From: Kevin McCarthy <kevin@8t8.us>
Date: Thu, 28 Dec 2017 21:07:21 +0000 (-0800)
Subject: Mention self_encrypt options in the documentation. (closes #3983)
X-Git-Tag: neomutt-20180223~48
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e03998414f5ae1fc16d89f8b6e69dcb0bc70ecda;p=neomutt

Mention self_encrypt options in the documentation. (closes #3983)

Add a paragraph to the "Sending Cryptographically Signed/Encrypted
Messages" section of the manual.
---

diff --git a/doc/manual.xml.head b/doc/manual.xml.head
index c597b9061..7c688764f 100644
--- a/doc/manual.xml.head
+++ b/doc/manual.xml.head
@@ -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