* mu4e: add note to doc about gpg-agent

This commit is contained in:
djcb
2012-10-29 16:03:52 +02:00
parent bb8bb20970
commit 3a5cb2d037

View File

@ -1149,21 +1149,31 @@ decryption of encrypted messages, as well as verification of signatures. For
signing/encrypting messages your outgoing messages, see @ref{Signing and
encrypting}.
Currently, only PGP/MIME is supported; PGP-inline and S/MIME are not.
Currently, only PGP/MIME is supported; PGP-inline and S/MIME are not.
For all of this to work, @command{gpg-agent} must be running, and it must set
the environment variable @t{GPG_AGENT_INFO}. You can check from
@command{emacs} with @key{M-x getenv GPG_AGENT_INFO}.
In many mainstream Linux/Unix desktop environments, everything works
out-of-the-box, but if your environment does not automatically start
@command{gpg-agent}, you can do so by hand:
@verbatim
$ eval $(gpg-agent --daemon)
@end verbatim
@noindent
This starts the daemon, and sets the environment variable.
@subsection Decryption
@anchor{Decryption}
If you receive messages that are encrypted (using PGP/MIME), @t{mu4e} can try
to decrypt them. For this, @t{gnupg-agent} must be running; in many mainstream
Linux/Unix desktop environments this should work automatically.
You can influence how @t{mu4e} deals with encrypted messages using
@code{mu4e-decryption-policy}. If you set it to @t{t}, @t{mu4e} attempts to
decrypt messages automatically; this is the default. If you set it to @t{nil},
@t{mu4e} @emph{won't} attempt to decrypt anything. Finally, if you set it to
@t{'ask}, it asks you what to do, each time an encrypted message is
encountered.
to decrypt them, base on the setting of @code{mu4e-decryption-policy}. If you
set it to @t{t}, @t{mu4e} attempts to decrypt messages automatically; this is
the default. If you set it to @t{nil}, @t{mu4e} @emph{won't} attempt to
decrypt anything. Finally, if you set it to @t{'ask}, it asks you what to do,
each time an encrypted message is encountered.
When opening an encrypted message, @t{mu} consults @t{gpg-agent} to see if it
already has unlocked the key needed to decrypt the message; if not, it prompts