Re: can't read sent encrypted mail

[Steve Schmerler]

On Oct 07 21:02 -0700, Kevin J. McCarthy wrote:
> On Sat, Oct 08, 2016 at 02:46:42AM +0200, Peter P. wrote:
[...]
> > How would I add my own key to the encryption in gpgme?
> 
> You could try adding an 'encrypt-to' setting in your ~/.gnupg/gpg.conf file.

Sorry for being late. I hit the same problem as Peter -- Debian's config
sets crypt_use_gpgme=yes in /etc/Muttrc.d/gpg.rc as of 1.7.x

I had the encrypt-to set in ~/.gnupg/gpg.conf before, which has the
downside that it will *always* encrypt with my key also outside of mutt,
where I might not want that. That's why I like the option of setting
--encrypt-to in gpg.rc using the classic interface -- restrict the
encrypt-to to mutt. Since gpgme is a gpg API, there seems to be no
gpgme.conf or such where one could set this option. Therefore, I'll use
the classic interface as long as it exists :)

best,
Steve

Re: can't read sent encrypted mail

[Peter P.]

* Kevin J. McCarthy  [2016-10-08 06:07]:
> On Sat, Oct 08, 2016 at 02:46:42AM +0200, Peter P. wrote:
> > Interesting! man muttrc tells me that the default for crypt_use_gpgme is no.
> 
> Yes, but I believe they changed the system muttrc to enable it (likely
> in /etc/Muttrc.d/gpg.rc.  Your own muttrc is read afterwards and so can
> override that setting.
> 
> > Nevertheless when I
> > unset crypt_use_gpgme
> > or
> > set unset crypt_use_gpgme=no
> > the problem remains.
> 
> Which problem are you speaking of?  This will not magically allow you to
> read emails encrypted in the recent past using gpgme (that therefore
> were not also encrypted to you).  It should make emails sent henceforth
> be encrypted to you again.
> 
> > How could I debug this further?
> 
> Well, first I am assuming that this is a recent change in behavior, and
> that prior to the mutt upgrade in Debian you had no trouble reading your
> encrypted emails sent to others.
> 
> You might check that those older sent emails are still readable by you.
> 
> To make sure the option is off, type
>   :set ?crypt_use_gpgme
> and mutt should echo back 'crypt_use_gpgme is unset'
Amazing idea, thank you! It made me find out that I had another line of 
set crypt_use_gpgme=yes
sneaked into my local mutt_gpg.rc by the debian maintainers. Removing
that made mutt use its old pgp_ commands and the self-encryption works
again.
 
Thanks Kevin!
P