On 16-05-15 03:27:20, Bob Holtzman wrote:
> On Fri, May 13, 2016 at 10:15:25PM +0200, Wim wrote:
> 
> After much screwing around I ran across the solution. I had been
> entering "p" in the compose window too early. After composing the
> message and hitting "escape" then ":wq" I hit "p" in the next window,
> the one where you normally enter "y" to send the message. Lo and behold
> the encryption menu appeared. Unfortunately that revealed another
> problem. When encrypting a test message, sending it, then going into the
> outbox and trying to decrypt it, it throws an error about the passphrase
> being invalid. A search turned up nothing applicable.
> 
> I'm at a loss to know where to start trying to troubleshoot this. 
> Any ideas?    
> 

This might be stupid and or too obvious but do you have yourself as a
gpg-recipient?

For example, I have the following in my .muttrc so that I can always
later on read my encrypted sent emails:

set pgp_encrypt_sign_command="/usr/lib/mutt/pgpewrap gpg2
--passphrase-fd 0 --batch --quiet --no-verbose \
--textmode --output - --encrypt --sign %?a?-u %a? --armor --always-trust
--encrypt-to 616BB08C -- -r %r -- %f"

If I leave out the "... --encrypt-to 616BB08C ..."-part then, _only_ 
the recipient(s) on the other end can decrypt the email.

Though some argue this is bad practice but I think it depends on your
use case. 

I'm not sure that this is your issue but I'm throwing this out there
anyway.

Regards.
-- 
Jonas Hedman 

XMPP:        n...@nstr.se
PGP Key:     0x5c3989e0616bb08c
Fingerprint: 8F72 C5BE AAFA B4BA 8F46  9185 5C39 89E0 616B B08C

Attachment: signature.asc
Description: Digital signature

Reply via email to