Re: Inline-encryption, encryption failure when storing sent mails

diff --git a/59/c3caffb8a1b30ba0cba6dc17b106c7b5b2c2bc b/59/c3caffb8a1b30ba0cba6dc17b106c7b5b2c2bc
new file mode 100644 (file)
index 0000000..be15167
--- /dev/null
+++ b/59/c3caffb8a1b30ba0cba6dc17b106c7b5b2c2bc
@@ -0,0 +1,74 @@
+Return-Path: <public@simonhirscher.de>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 7304C431E64\r
+       for <notmuch@notmuchmail.org>; Fri, 16 Aug 2013 04:33:30 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.363\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.363 tagged_above=-999 required=5\r
+       tests=[RDNS_DYNAMIC=0.363] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id esufIGGTuTnu for <notmuch@notmuchmail.org>;\r
+       Fri, 16 Aug 2013 04:33:25 -0700 (PDT)\r
+Received: from cloudia.org (lvps176-28-19-116.dedicated.hosteurope.de\r
+       [176.28.19.116])\r
+       (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 37B58431FAF\r
+       for <notmuch@notmuchmail.org>; Fri, 16 Aug 2013 04:33:25 -0700 (PDT)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+       d=google.com; s=20120113;\r
+       h=mime-version:in-reply-to:references:from:date:message-id:subject:to\r
+       :cc:content-type;\r
+       bh=PToh7h0fK6NdWNgHHTen9vl7VM9GPuYzWyxywXB4AFI=;\r
+       b=ekPL3HGMyvxbs1apI524jt0G1acroXqMyyGPtOx/jkN52T7cpkJHydV6PjnY5gJOYp\r
+       tNUCsxe03kGfgIbzEtRFfK5Bm6FikmwRrYZ7WMONkIRuq1mda2qvqILq+wQOcGnogYtk\r
+       Zfb1DGdmtjmYQOzts+VuD59iS5LD2igf8uPCU/WKMdTlj07DHzG1C+qUvfOAzIXpP7ur\r
+       OY6eMLlgx4kwHQknIjlQyaUjvEh7xarVXp5L2sxmVfr3rdakRQNggVBnrl4ca8E95dXn\r
+       TWnDUq+Lnje20I4w/fK9gxvNMIgS/D2xsYTqzCaOqoIc4L/nSahqZKm12PvQhpIZ+2kI\r
+       3Tyg==\r
+X-Received: by 10.112.42.68 with SMTP id m4mr2023461lbl.4.1376652799477; Fri,\r
+       16 Aug 2013 04:33:19 -0700 (PDT)\r
+MIME-Version: 1.0\r
+In-Reply-To: <878v02ysfg.fsf@maritornes.cs.unb.ca>\r
+References:\r
+ <CAEj42wtJzxjQKCMQKZ3354oEnW5+McxvzLaM4q9Yx19nR6H_mQ@mail.gmail.com>\r
+       <878v02ysfg.fsf@maritornes.cs.unb.ca>\r
+From: Simon Hirscher <public@simonhirscher.de>\r
+Date: Fri, 16 Aug 2013 13:32:49 +0200\r
+Message-ID:\r
+ <CAEj42ws1arpca6NqRc1ZL8rrVdBCK4W4ijmxUq3AnScBoxKupA@mail.gmail.com>\r
+Subject: Re: Inline-encryption, encryption failure when storing sent mails\r
+To: David Bremner <david@tethera.net>\r
+Content-Type: text/plain; charset=UTF-8\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Fri, 16 Aug 2013 11:33:30 -0000\r
+\r
+On Fri, Aug 16, 2013 at 10:02 AM, David Bremner <david@tethera.net> wrote:\r
+> What about setting this on the gpg level with the "encrypt-to" option?\r
+> Setting the emacs variable mml2015-encrypt-to-self seems like it ought\r
+> to work, but it seems to need some other settings as well. Perhaps have\r
+> a look at the customization group 'mime-security'.\r
+\r
+Thanks, this was exactly what I was looking for! Although, there seems\r
+to be a pitfall regarding recipients that I don't have a public key\r
+for: If I choose to skip the encryption when sending the message, it\r
+will still be encrypted with my own public key, hence the recipient\r
+won't be able to read it. In that case it's obviously better to remove\r
+the encryption tag from the message body before sending.\r