Re: Encrypt gcc copy with own key

[Daiki Ueno <ueno@unixuser.org>]

>>>>> In <y9liqjlfr5a.fsf@deinprogramm.de> 
>>>>>	Michael Sperber <sperber@deinprogramm.de> wrote:

> > Try "encrypt-to <your key ID>" instead of "default-recipient-self".

> Doesn't work for me

It works for me.

> tracing through the code,

I'd suggest you to try it from the command line before looking into the
Lisp code.  I.e.

 $ gpg --encrypt-to sperber@deinprogramm.de -e -r foo@example.com test.txt
 $ gpg < test.txt.gpg

> I see that the recipient key (i.e. not mine) is *explicitly* used for
> archiving the Gcc copy.  The key is propagated from one invocation of
> `mml2015-epg-encrypt' to the next via the `mml2015-epg-recipients'
> message option.

Yes, that is correct behavior.  "encrypt-to sperber@deinprogramm.de" in
gpg.conf makes your address an *additional* recipient for all the
outgoing messages, while "default-recipent-self" doesn't.

Regards,
-- 
Daiki Ueno