summaryrefslogtreecommitdiff
path: root/docs/source/usage
diff options
context:
space:
mode:
authorLucas Hoffmann <l-m-h@web.de>2015-12-08 18:13:25 +0100
committerLucas Hoffmann <l-m-h@web.de>2015-12-08 18:15:30 +0100
commit4111ee7685c27ca7144a9e49fe18392c3d01d0a9 (patch)
tree9cffa77679a3e39675468c8178dcf4634260c7f2 /docs/source/usage
parentc8c06043be944003aa3a932845c0c5d1d9a9f92c (diff)
Add comment about "encrypt-to-self" in docs.
Diffstat (limited to 'docs/source/usage')
-rw-r--r--docs/source/usage/crypto.rst6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/source/usage/crypto.rst b/docs/source/usage/crypto.rst
index 6cee7753..243cc445 100644
--- a/docs/source/usage/crypto.rst
+++ b/docs/source/usage/crypto.rst
@@ -39,3 +39,9 @@ and :ref:`toggleencrypt <cmd.envelope.toggleencrypt>` and
in envelope mode to ask alot to encrypt the mail before sending.
The :ref:`encrypt <cmd.envelope.encrypt>` command accepts an optional
hint string as argument to determine the key of the recipient.
+
+If you want to access encrypt mail later it is useful to add yourself to the
+list of recipients when encrypting with gpg (not the recipients whom mail is
+actually send to). The simplest way to do this is to use the `encrypt-to`
+option in the :file:`~/.gnupg/gpg.conf`. But you might have to specify the
+correct encryption subkey otherwise gpg seems to throw an error.