From: Ruben Pollan <meskio@sindominio.net>
To: Patrick Totzke <patricktotzke@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [alot] announcing v0.3.5
Date: Fri, 19 Jul 2013 17:01:06 +0200 [thread overview]
Message-ID: <20130719150106.6257.25551@hermes> (raw)
In-Reply-To: <20130719140234.25629.48004@megatron>
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
Quoting Patrick Totzke (2013-07-19 16:02:34)
> Hi Rubén,
>
> thanks for mentioning this. I must have accidentally dropped the corresponding paragraph
> in the docs (http://alot.readthedocs.org/en/testing/usage/index.html#cryptography).
> I'm almost certain I saw this documented a while back..
>
> Basically, you need a running gpg-agent. Then, decryption of mails should happen
> automatically once you open a thread. The same holds for signature verification
> (the status of which will be mentioned in a pseudo-header).
> This holds for mails that comply PGP/MIME only. "ASCII-armored" text in plaintext parts
> is not dealt with.
>
> If this does not work, you've found a bug that you should kindly report :)
Sadly that is not what I see. I'm trying to read an email that mutt reports as
PGP/MIME but the content appear blank. I guess I have gpg-agent properly
working, because when I send a signed email I get a 'window' asking me for my
passphrase and it signs it. But it don't asks for the password when I try to
read an encrypted email.
Do I need any special configuration on gpg-agent for it?
--
Rubén Pollán | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iEYEABECAAYFAlHpVLIACgkQGKOQ92SwNMKVgACdG1bZS+lmlQFoCotQEZ/2BpZd
G0oAmwe1e8+yaJUZM+BODzCzsj94hY7N
=nPTj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-07-19 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 9:21 [alot] announcing v0.3.5 Patrick Totzke
2013-07-19 13:48 ` Ruben Pollan
2013-07-19 14:02 ` Patrick Totzke
2013-07-19 15:01 ` Ruben Pollan [this message]
2013-07-19 15:14 ` Patrick Totzke
2013-07-19 15:24 ` Ruben Pollan
2013-07-19 15:30 ` Patrick Totzke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130719150106.6257.25551@hermes \
--to=meskio@sindominio.net \
--cc=notmuch@notmuchmail.org \
--cc=patricktotzke@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).