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

diff --git a/09/0a2a9ff110be4eed0e9b5b6f8f3839c107663b b/09/0a2a9ff110be4eed0e9b5b6f8f3839c107663b
new file mode 100644 (file)
index 0000000..3fe6710
--- /dev/null
+++ b/09/0a2a9ff110be4eed0e9b5b6f8f3839c107663b
@@ -0,0 +1,111 @@
+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 0E946429E26\r
+       for <notmuch@notmuchmail.org>; Thu, 12 Jan 2012 10:41:42 -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 I9+Y-FsbqvNX for <notmuch@notmuchmail.org>;\r
+       Thu, 12 Jan 2012 10:41:40 -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 1DA6A431FB6\r
+       for <notmuch@notmuchmail.org>; Thu, 12 Jan 2012 10:41:40 -0800 (PST)\r
+Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])\r
+       by fire-doxen-postvirus (Postfix) with ESMTP id 90E1432803F\r
+       for <notmuch@notmuchmail.org>; Thu, 12 Jan 2012 10:41:39 -0800 (PST)\r
+X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new\r
+Received: from finestructure.net (DHCP-123-180.caltech.edu [131.215.123.180])\r
+       (Authenticated sender: jrollins)\r
+       by fire-doxen-submit (Postfix) with ESMTP id 86D902E50408\r
+       for <notmuch@notmuchmail.org>; Thu, 12 Jan 2012 10:41:34 -0800 (PST)\r
+Received: by finestructure.net (Postfix, from userid 1000)\r
+       id 62A478A; Thu, 12 Jan 2012 10:41:34 -0800 (PST)\r
+From: Jameson Graef Rollins <jrollins@finestructure.net>\r
+To: Notmuch Mail <notmuch@notmuchmail.org>\r
+Subject: Re: Emacs: Crypto: How to get automatic encryption?\r
+In-Reply-To: <87fwfw8npx.fsf@servo.finestructure.net>\r
+References: <20120103195651.GA27869@shi.workgroup>\r
+       <87fwfw8npx.fsf@servo.finestructure.net>\r
+User-Agent: Notmuch/0.10.2+168~g34b8bac (http://notmuchmail.org) Emacs/23.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Thu, 12 Jan 2012 10:41:31 -0800\r
+Message-ID: <87k44wlq5g.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: Thu, 12 Jan 2012 18:41:42 -0000\r
+\r
+--=-=-=\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Tue, 03 Jan 2012 13:45:14 -0800, Jameson Graef Rollins <jrollins@finestr=\r
+ucture.net> wrote:\r
+> Unfortunately, auto encrypting of replies to encrypted emails is not yet\r
+> implemented.  It is desperately needed, though, obviously.  So this is a\r
+> good excuse to start a discussion about how we could achieve this.\r
+>=20\r
+> It just occurs to me that a way to do this would be to have notmuch\r
+> reply add the appropriate mml #secure tag for encryption to the output\r
+> reply template, maybe with something like a --emacs option.  That would\r
+> be pretty easy to implement, although it would obviously be very UI\r
+> specific.\r
+>=20\r
+> Another possibility would be for notmuch reply to add some sort of\r
+> header to the reply message to indicate that the original was encrypted,\r
+> and then do something in emacs to try to read that header and add the\r
+> appropriate mml #secure tag.  That would also be easy to implement in\r
+> the notmuch CLI, and it would be more UI agnostic, but it would require\r
+> a lot more elisp.\r
+\r
+There is a set of patches in the queue to add a JSON output format for\r
+reply, with the emacs UI then consuming that to construct the reply\r
+template [0].  This will make it very easy to communicate to the emacs\r
+UI that the original message was encrypted, and that the reply should be\r
+similarly encrypted.  I'm going to wait until that patch set makes it\r
+through, and then build this functionality on top of that.\r
+\r
+jamie.\r
+\r
+[0] id:"1326009162-19524-3-git-send-email-awg+notmuch@xvx.ca"\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.11 (GNU/Linux)\r
+\r
+iQIcBAEBCAAGBQJPDylcAAoJEO00zqvie6q8soAP/0WkpELUJo702xcVnxV0l/4e\r
+SMzDe7GWjrUMdTeR4+ee0nkbAGFOJhXFN4VOG+WCKNdMjOUOa5b3SN9Hj0nZESxg\r
+LvSKBPzyjDz3/Fet5HEGgcD1KkjPWwOKlqb6ehSSi99O4DRRoKxLCgtlNK1jy1nb\r
+CxkQ4WC4FzLDQxJZZ3ym86hr+q9hV0wMtz+P1CyMTYBQGIwHpVw5knttT6JJrH31\r
+1ZtR5RUDykdgasuoWblQkYRffPuwV6O9/V7Hzmhi2Ki/dg/m7+EZER2ESu12FhHa\r
+IoL/PfukALXmW1f1PmDyjE7RTWEhtfLwwYjy5eymL0TAW2pRC+A6DBcLZru7iV1x\r
+0KzO85VWTPr3VkGZ9uV3a2rNTXWcCsZPC6GWktpxaaDzX+JoK+KcjSvL9rafjt+X\r
+gyQuIeHK76PrbLMUdWakACQNzqFavCdMC9jKFthcIAoPtZlxV6kQvLnsz5nR2hqR\r
+Aowo9CLhV965wDlL6zC61xVFYII469SkXpXbjjZ0SAz/vZ0NArzSbQrcqmbCoWhd\r
+Ag3DlyxosYcWLU68eUmT4lO+W8Qo4L8uIrjDNXbZ+xCV1eRvf5uf2+aN6IOMtjya\r
+13neYw3M2Lzxins0D6wYHJRrr63IzFR1utZs6oI05JsASJV6JRRSvE/A4qTXMtT9\r
+YXK1ioq/NVGRaSpqJRI3\r
+=80nC\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r