encrypting replies to encrypted mail

diff --git a/b6/92bde7847ea52fc91e2c7e98c1058a08e50c4d b/b6/92bde7847ea52fc91e2c7e98c1058a08e50c4d
new file mode 100644 (file)
index 0000000..a67ddea
--- /dev/null
+++ b/b6/92bde7847ea52fc91e2c7e98c1058a08e50c4d
@@ -0,0 +1,107 @@
+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 953B1431E84\r
+       for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 11:25:03 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.3\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3] 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 nEbQm+17xvKF for <notmuch@notmuchmail.org>;\r
+       Sun, 12 Jan 2014 11:24:56 -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 440F4431E82\r
+       for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 11:24:56 -0800 (PST)\r
+Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])\r
+       by fire-doxen-postvirus (Postfix) with ESMTP id C894132800A\r
+       for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 11:24:53 -0800 (PST)\r
+X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new\r
+Received: from finestructure.net (wsip-98-175-145-180.no.no.cox.net\r
+       [98.175.145.180]) (Authenticated sender: jrollins)\r
+       by fire-doxen-submit (Postfix) with ESMTP id 406472E50E87\r
+       for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 11:24:52 -0800 (PST)\r
+Received: by finestructure.net (Postfix, from userid 1000)\r
+       id 16839600A3; Sun, 12 Jan 2014 11:24:48 -0800 (PST)\r
+From: Jameson Graef Rollins <jrollins@finestructure.net>\r
+To: Notmuch Mail <notmuch@notmuchmail.org>\r
+Subject: encrypting replies to encrypted mail\r
+User-Agent: Notmuch/0.17+9~g39408d0 (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Sun, 12 Jan 2014 11:24:45 -0800\r
+Message-ID: <87a9f1c8aq.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: Sun, 12 Jan 2014 19:25:03 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+\r
+Hi, folks.  I've been worried for a while about the fact that my notmuch\r
+mua (notmuch-emacs) does not automatically encrypt replies to encrypted\r
+messages.  Recently my fears came true when I accidentally sent in the\r
+clear a reply to an encrypted message that include a full quote of the\r
+original encrypted text.  This is obviously not ok, to the extent that I\r
+would like to now consider this a UI bug in notmuch-emacs.\r
+\r
+The question is how do we solve this problem.  The tricky bit is that\r
+notmuch-emacs uses message-mode to compose and send messages, and mml to\r
+handle signing and encrypting, but uses the binary "reply" command to\r
+generate reply bodies.  message-mode therefore does not know if the\r
+original message was encrypted or not.\r
+\r
+One proposal would be to add a switch to the reply command that would\r
+insert the mml "signencrypt" header [0] to the top of reply bodies if\r
+the message being replied to was encrypted.  Something like\r
+"--mml-encrypt" or something like that.  It's a fix targeted to a\r
+particular work flow/setup, but it might cover enough use cases to make\r
+it still be worthwhile.\r
+\r
+What do people think?  Any other ideas for solving this issue?  I note\r
+that there are other emacs tricks for dealing with encrypting messages\r
+[1], but none that I have found would solve this particular situation.\r
+\r
+jamie.\r
+\r
+[0] https://www.gnu.org/software/emacs/manual/html_node/mh-e/Sending-PGP.html\r
+[1] http://www.emacswiki.org/emacs/DefaultEncrypt\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.15 (GNU/Linux)\r
+\r
+iQIcBAEBCAAGBQJS0uv9AAoJEO00zqvie6q85/AP/RMm36GO9SSbID/hjnEajncS\r
++y0VD1AF2JIEOp+X58JXYPX4kGPw4QSdnC1FkckwjRzF2Ms8BAWwd0UMrrm0PdyF\r
+LJ/VQD/vP7jeLu3d4jj9NJdnEHYCwshbBoW1XX0xpO7ygoRG2cAzC0DfE8Qfy2rN\r
+0UJCvfAep+ufZSunucM628pRNoqvu+MnJHDVI94leXFHyWda2VmvBbIJJwCRcNBi\r
+m61oWIBu+l28wZNIRqQeM8Cnwmf+Ty9p4IzyBdHSt0XotNcr9Ha1EP6Jx6n0+KHg\r
+35ZobBGeW683SD2rJHm4431DZ1V4dzfIt8YnUaYF9NriuC0VkK6QBHROUm/t3coy\r
+yJ21PBGOFHfwuZa4ob0HJ60GZyZCePRsy8fLHnkRC06qk1aI4qq2wNs1Ymyxhl4d\r
+ulEvwv5u13UwI3CBtf0cOhqMtjUOYkm+U/XsXHJZ+OJooP1bF9t6pSw9rq9jR+DU\r
+dHKeKddxG+A9JdD9jRpvCDkcD1pWRW2w8Z5Zi02gHzM/GM1HC05JyQH/GhJq08ME\r
+Ay+PxyXTQDgeFVWdczZ4hyJ/sqGOFx+9OZ2wOIkZPtKy+MCtoy4ajsQZxD1CSaB7\r
+ey8/CFkiffnHttgcdVS/UmPxRaF9N92e2PbPCnSjiND4zRszG1OxHCd9+FubqNpA\r
+UiWSFQHfQrtbsS78AFqD\r
+=CG7m\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r