Re: Emacs: Crypto: How to get automatic encryption?

diff --git a/c4/89f862108fad3396d31baa50f5bbbda350dd6a b/c4/89f862108fad3396d31baa50f5bbbda350dd6a
new file mode 100644 (file)
index 0000000..678ee1d
--- /dev/null
+++ b/c4/89f862108fad3396d31baa50f5bbbda350dd6a
@@ -0,0 +1,112 @@
+Return-Path: <jrollins@finestructure.net>\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 CF28B429E39\r
+       for <notmuch@notmuchmail.org>; Wed, 25 Jan 2012 09:45:07 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.29\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3, T_MIME_NO_TEXT=0.01] 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 vHzdedu8SF2V for <notmuch@notmuchmail.org>;\r
+       Wed, 25 Jan 2012 09:45:07 -0800 (PST)\r
+Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu\r
+       [131.215.239.19])\r
+       by olra.theworths.org (Postfix) with ESMTP id 40DDA431FBC\r
+       for <notmuch@notmuchmail.org>; Wed, 25 Jan 2012 09:45:07 -0800 (PST)\r
+Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])\r
+       by fire-doxen-postvirus (Postfix) with ESMTP id B2012328092;\r
+       Wed, 25 Jan 2012 09:45:06 -0800 (PST)\r
+X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new\r
+Received: from finestructure.net (cpe-76-174-137-84.socal.res.rr.com\r
+       [76.174.137.84]) (Authenticated sender: jrollins)\r
+       by fire-doxen-submit (Postfix) with ESMTP id F048A328094;\r
+       Wed, 25 Jan 2012 09:45:03 -0800 (PST)\r
+Received: by finestructure.net (Postfix, from userid 1000)\r
+       id 9EC9E2A9; Wed, 25 Jan 2012 09:45:03 -0800 (PST)\r
+From: Jameson Graef Rollins <jrollins@finestructure.net>\r
+To: David Edmondson <dme@dme.org>, Notmuch Mail <notmuch@notmuchmail.org>\r
+Subject: Re: Emacs: Crypto: How to get automatic encryption?\r
+In-Reply-To: <cund3a8nkwl.fsf@hotblack-desiato.hh.sledj.net>\r
+References: <87pqejj5nl.fsf@marcos.anarcat.ath.cx>\r
+       <cunfwfer8i0.fsf@hotblack-desiato.hh.sledj.net>\r
+       <87ehuo7pjr.fsf@algae.riseup.net>\r
+       <87ehuoljzs.fsf@servo.finestructure.net>\r
+       <cunvco0nvwa.fsf@hotblack-desiato.hh.sledj.net>\r
+       <87liow6slg.fsf@servo.finestructure.net>\r
+       <cund3a8nkwl.fsf@hotblack-desiato.hh.sledj.net>\r
+User-Agent: Notmuch/0.11+115~g51d071f (http://notmuchmail.org) Emacs/23.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Wed, 25 Jan 2012 09:45:01 -0800\r
+Message-ID: <878vkv7k2q.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha256; protocol="application/pgp-signature"\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: Wed, 25 Jan 2012 17:45:07 -0000\r
+\r
+--=-=-=\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Wed, 25 Jan 2012 10:20:26 +0000, David Edmondson <dme@dme.org> wrote:\r
+> Isn't it still necessary to ensure that you have encryption keys\r
+> appropriate to the recipient?\r
+\r
+I want to ensure that all replies to encrypted to be encrypted.  I would\r
+rather have the reply fail outright than fall back to unencrypted.\r
+\r
+Here's a behavior that I think would be reasonable:\r
+\r
+ * notmuch reply outputs JSON encrypted flag\r
+\r
+ * emacs does a quick check to see if the needed key is available\r
+\r
+ * if key not available: give a nice mini-buffer prompt, something like:\r
+=20\r
+    'encryption key for "Foo Bar <foo@bar.com>" not found.  Retrieve?'\r
+\r
+   * if response is yes: call gpg to retrieve the key\r
+\r
+ * if key available: add encrypt flag\r
+\r
+   else: I feel like this should abort, but maybe there's something to\r
+         be done here.  Allow reply but don't quote the original?\r
+\r
+jamie.\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.11 (GNU/Linux)\r
+\r
+iQIcBAEBCAAGBQJPID+dAAoJEO00zqvie6q8B7oP/0jggtsnGKAy0yuVUXbXSu+X\r
+vyNNKwbG2EHVW0wYA7QkHtTQfClkUXPZLWWwyEw0L2LBT3TViDpyCtwu2/fOHEvH\r
+7kv/uS8xGj6hwtVboOjeoZnTTW/M9k+mLMEEkyX/WWX5+2TVVUJxRjWZuf2feMgs\r
+5R72vtIowlWIIyN5LQjxxxkX+3+yHEOG9RcZWO4vGCfF+UWRWQDc7pl3is5AIq8v\r
+8bHMmqiARLqb4HXQZItGHwcKIQUm3SiJeDddvMKc7DC/TKMLGd9SAiDKCcDLKC2Z\r
+eXviRL81B2rm0xlV/Sh3XnesWOfx2ZGmszmYdlA+LEdZ54QSO/rE0PDy+cWwJ98m\r
+iWck+RFyHKcIp/w8mJMCWriKWJoRVKB/vqbP9Fk2LlnB71lVBUXOqLM3RxddIkXN\r
+avaO2nORPEs7TUumyeAwrzMrkmv62Isx7Fx89z7vwrLh91pPbAOgsoV6EQPCHzwR\r
+RS6BvUfLRr9XHcy/yVEvLZJSyiTIPXYPxnhLOYd0x8bs8hfjYNMO6vj2PogR9oUG\r
+HmO3U7AGS4u5wrOykN6F8qTbDuA4YBqJBBexUrWCnUAMuTj9W5zs3i2GKp8l0/IJ\r
+LxGPIDgVNwDWQR/bNomMOLIEgFuKM3eE1V7nqiaPJLYj/aK7NWAcM60lUU9sfN2n\r
+zd4ILBrLkOz9fNp9U0FD\r
+=PETs\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r