MIME-Version: 1.0
In-Reply-To: <878v02ysfg.fsf@maritornes.cs.unb.ca>
References:
 <CAEj42wtJzxjQKCMQKZ3354oEnW5+McxvzLaM4q9Yx19nR6H_mQ@mail.gmail.com>
	<878v02ysfg.fsf@maritornes.cs.unb.ca>
From: Simon Hirscher <public@simonhirscher.de>
Date: Fri, 16 Aug 2013 13:32:49 +0200
Message-ID:
 <CAEj42ws1arpca6NqRc1ZL8rrVdBCK4W4ijmxUq3AnScBoxKupA@mail.gmail.com>
Subject: Re: Inline-encryption, encryption failure when storing sent mails
To: David Bremner <david@tethera.net>
Content-Type: text/plain; charset=UTF-8
Cc: notmuch@notmuchmail.org
Precedence: list

On Fri, Aug 16, 2013 at 10:02 AM, David Bremner <david@tethera.net> wrote:
> What about setting this on the gpg level with the "encrypt-to" option?
> Setting the emacs variable mml2015-encrypt-to-self seems like it ought
> to work, but it seems to need some other settings as well. Perhaps have
> a look at the customization group 'mime-security'.

Thanks, this was exactly what I was looking for! Although, there seems
to be a pitfall regarding recipients that I don't have a public key
for: If I choose to skip the encryption when sending the message, it
will still be encrypted with my own public key, hence the recipient
won't be able to read it. In that case it's obviously better to remove
the encryption tag from the message body before sending.