Re: Mutt/GPG: *un*encrypted copies to self?

2004-10-09 Thread Shot (Piotr Szotkowski)
Hello. Martin Dickopp: > a standard solution to this problem is to encrypt the message with > your own key in addition to the recipient's key. GnuPG will do this > automatically if you put the line > > encrypt-to "your-key-id" > > in your ~/.gnupg/gpg.conf file. Thanks, Martin, Johann and

Re: Mutt/GPG: *un*encrypted copies to self?

2004-10-08 Thread Martin Dickopp
"Shot (Piotr Szotkowski)" <[EMAIL PROTECTED]> writes: > Recently I started learning how to use GPG for signing and encrypting my > mail, and today noticed that the outgoing encrypted messages are copied > into $record folder *after* the encryption; as you can imagine, this > makes them quite usele

Re: Mutt/GPG: *un*encrypted copies to self?

2004-10-08 Thread Andreas Janssen
Hello Shot (Piotr Szotkowski) (<[EMAIL PROTECTED]>) wrote: > Recently I started learning how to use GPG for signing and encrypting > my mail, and today noticed that the outgoing encrypted messages are > copied into $record folder *after* the encryption; as you can imagine, > this makes them quite

Mutt/GPG: *un*encrypted copies to self?

2004-10-08 Thread Shot (Piotr Szotkowski)
Hello. Recently I started learning how to use GPG for signing and encrypting my mail, and today noticed that the outgoing encrypted messages are copied into $record folder *after* the encryption; as you can imagine, this makes them quite useless for me, as I don't have the recipient's private key.