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

diff --git a/02/15c492ca20ed567f73292f7e5a281f8edb3f2a b/02/15c492ca20ed567f73292f7e5a281f8edb3f2a
new file mode 100644 (file)
index 0000000..cea0703
--- /dev/null
+++ b/02/15c492ca20ed567f73292f7e5a281f8edb3f2a
@@ -0,0 +1,95 @@
+Return-Path: <dme@dme.org>\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 8B70E431FD5\r
+       for <notmuch@notmuchmail.org>; Tue, 24 Jan 2012 22:23:06 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_LOW=-0.7] 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 AIY2AnqmaxR5 for <notmuch@notmuchmail.org>;\r
+       Tue, 24 Jan 2012 22:23:06 -0800 (PST)\r
+Received: from mail-we0-f181.google.com (mail-we0-f181.google.com\r
+       [74.125.82.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id B5176431FB6\r
+       for <notmuch@notmuchmail.org>; Tue, 24 Jan 2012 22:23:05 -0800 (PST)\r
+Received: by werb10 with SMTP id b10so4125382wer.26\r
+       for <notmuch@notmuchmail.org>; Tue, 24 Jan 2012 22:23:04 -0800 (PST)\r
+Received: by 10.216.137.219 with SMTP id y69mr6482521wei.51.1327472584685;\r
+       Tue, 24 Jan 2012 22:23:04 -0800 (PST)\r
+Received: from hotblack-desiato.hh.sledj.net\r
+       (host81-149-164-25.in-addr.btopenworld.com. [81.149.164.25])\r
+       by mx.google.com with ESMTPS id j16sm22002181wie.4.2012.01.24.22.23.02\r
+       (version=TLSv1/SSLv3 cipher=OTHER);\r
+       Tue, 24 Jan 2012 22:23:03 -0800 (PST)\r
+Received: by hotblack-desiato.hh.sledj.net (Postfix, from userid 30000)\r
+       id 98EB69FD47; Wed, 25 Jan 2012 06:23:01 +0000 (GMT)\r
+To: Jameson Graef Rollins <jrollins@finestructure.net>,\r
+       Notmuch Mail <notmuch@notmuchmail.org>\r
+Subject: Re: Emacs: Crypto: How to get automatic encryption?\r
+In-Reply-To: <87ehuoljzs.fsf@servo.finestructure.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
+User-Agent: Notmuch/0.11+105~g08b3b0f (http://notmuchmail.org) Emacs/24.0.92.1\r
+       (x86_64-pc-linux-gnu)\r
+From: David Edmondson <dme@dme.org>\r
+Date: Wed, 25 Jan 2012 06:23:01 +0000\r
+Message-ID: <cunvco0nvwa.fsf@hotblack-desiato.hh.sledj.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha1; protocol="application/pgp-signature"\r
+X-Gm-Message-State:\r
+ ALoCoQmFxB/qAz+KKtiR/Wvaz8NEK3SgdmkKSLDoFle0LFoFSLS47tKxl+E+UXD9mRk27Wre/KRg\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 06:23:06 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Tue, 24 Jan 2012 16:10:47 -0800, Jameson Graef Rollins <jrollins@finestr=\r
+ucture.net> wrote:\r
+> On Tue, 24 Jan 2012 16:34:32 -0500, micah anderson <micah@riseup.net> wro=\r
+te:\r
+> > David replied to it because it was sent to him, but the list email\r
+> > hasn't come through yet (I want this functionality, so I'm dying to see\r
+> > the patch!)\r
+>=20\r
+> Hey, Micah.  There an outstanding patch series that add a new JSON reply\r
+> format, and then uses that in emacs [0].  Once that's in, it will be\r
+> relatively easy to implement auto-reply-to-encrypted.  I'm going to work\r
+> on implementing that as soon as the above patch gets pushed to master.\r
+\r
+Can you explain the logic that will apply to determine whether or not a\r
+reply is encrypted?\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.11 (GNU/Linux)\r
+\r
+iEYEARECAAYFAk8fn8UACgkQaezQq/BJZRYi/QCcCeUqYq5fNKDSM8TNAL1xg40p\r
+VvMAn0KxOgKhKEuzB8lQNGVtSx+Td9wj\r
+=UQQn\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r