On Tue, Sep 20, 2016 at 10:51:01AM +0200, Christian Pietsch wrote: > Dear Maintainer, > > * What led up to the situation? > > Version 1.7.0-5 enabled GPGME for PGP handling by default. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > After updating to version 1.7.0-5, when I sent an encrypted e-mail to > somebody else, I was surprised that I was unable to decrypt this > message afterwards. > > Before the upgrade, I was able to decrypt all PGP/MIME messages I had > sent. > > * My analysis: > > It turns out I did not have `set pgp_encrypt_self=yes` in my > configuration. Instead, I relied on the following settings which seem > to be ignored by GPGME: > > set pgp_encrypt_only_command="/usr/lib/mutt/pgpewrap gpg --batch --quiet > --no-verbose --output - --encrypt --textmode --armor --always-trust > --encrypt-to 0x0000000000000000 > set pgp_encrypt_sign_command="/usr/lib/mutt/pgpewrap gpg --passphrase-fd 0 > --batch --quiet --no-verbose --textmode --output - --encrypt --sign %?a?-u > %a? --armor --always-trust --encrypt-to 0x0000000000000000 -- -r %r -- %f" > > Would it be possible to honour these settings with GPGME, or to parse > the `--encrypt-to` argument to make the transition to GPGME a smoother > experience? >
Just to clarify this to myself, pgp_encrypt_self=true is going to solve this, the bug itself is for a smoother transition if --encrypt-to is set in the pgp_ commands