1 Return-Path: <jrollins@finestructure.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 953B1431E84
\r
6 for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 11:25:03 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id nEbQm+17xvKF for <notmuch@notmuchmail.org>;
\r
16 Sun, 12 Jan 2014 11:24:56 -0800 (PST)
\r
17 Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu
\r
19 by olra.theworths.org (Postfix) with ESMTP id 440F4431E82
\r
20 for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 11:24:56 -0800 (PST)
\r
21 Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])
\r
22 by fire-doxen-postvirus (Postfix) with ESMTP id C894132800A
\r
23 for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 11:24:53 -0800 (PST)
\r
24 X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new
\r
25 Received: from finestructure.net (wsip-98-175-145-180.no.no.cox.net
\r
26 [98.175.145.180]) (Authenticated sender: jrollins)
\r
27 by fire-doxen-submit (Postfix) with ESMTP id 406472E50E87
\r
28 for <notmuch@notmuchmail.org>; Sun, 12 Jan 2014 11:24:52 -0800 (PST)
\r
29 Received: by finestructure.net (Postfix, from userid 1000)
\r
30 id 16839600A3; Sun, 12 Jan 2014 11:24:48 -0800 (PST)
\r
31 From: Jameson Graef Rollins <jrollins@finestructure.net>
\r
32 To: Notmuch Mail <notmuch@notmuchmail.org>
\r
33 Subject: encrypting replies to encrypted mail
\r
34 User-Agent: Notmuch/0.17+9~g39408d0 (http://notmuchmail.org) Emacs/24.3.1
\r
35 (x86_64-pc-linux-gnu)
\r
36 Date: Sun, 12 Jan 2014 11:24:45 -0800
\r
37 Message-ID: <87a9f1c8aq.fsf@servo.finestructure.net>
\r
39 Content-Type: multipart/signed; boundary="=-=-=";
\r
40 micalg=pgp-sha256; protocol="application/pgp-signature"
\r
41 X-BeenThere: notmuch@notmuchmail.org
\r
42 X-Mailman-Version: 2.1.13
\r
44 List-Id: "Use and development of the notmuch mail system."
\r
45 <notmuch.notmuchmail.org>
\r
46 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
47 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
48 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
49 List-Post: <mailto:notmuch@notmuchmail.org>
\r
50 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
51 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
52 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
53 X-List-Received-Date: Sun, 12 Jan 2014 19:25:03 -0000
\r
56 Content-Type: text/plain
\r
58 Hi, folks. I've been worried for a while about the fact that my notmuch
\r
59 mua (notmuch-emacs) does not automatically encrypt replies to encrypted
\r
60 messages. Recently my fears came true when I accidentally sent in the
\r
61 clear a reply to an encrypted message that include a full quote of the
\r
62 original encrypted text. This is obviously not ok, to the extent that I
\r
63 would like to now consider this a UI bug in notmuch-emacs.
\r
65 The question is how do we solve this problem. The tricky bit is that
\r
66 notmuch-emacs uses message-mode to compose and send messages, and mml to
\r
67 handle signing and encrypting, but uses the binary "reply" command to
\r
68 generate reply bodies. message-mode therefore does not know if the
\r
69 original message was encrypted or not.
\r
71 One proposal would be to add a switch to the reply command that would
\r
72 insert the mml "signencrypt" header [0] to the top of reply bodies if
\r
73 the message being replied to was encrypted. Something like
\r
74 "--mml-encrypt" or something like that. It's a fix targeted to a
\r
75 particular work flow/setup, but it might cover enough use cases to make
\r
76 it still be worthwhile.
\r
78 What do people think? Any other ideas for solving this issue? I note
\r
79 that there are other emacs tricks for dealing with encrypting messages
\r
80 [1], but none that I have found would solve this particular situation.
\r
84 [0] https://www.gnu.org/software/emacs/manual/html_node/mh-e/Sending-PGP.html
\r
85 [1] http://www.emacswiki.org/emacs/DefaultEncrypt
\r
88 Content-Type: application/pgp-signature
\r
90 -----BEGIN PGP SIGNATURE-----
\r
91 Version: GnuPG v1.4.15 (GNU/Linux)
\r
93 iQIcBAEBCAAGBQJS0uv9AAoJEO00zqvie6q85/AP/RMm36GO9SSbID/hjnEajncS
\r
94 +y0VD1AF2JIEOp+X58JXYPX4kGPw4QSdnC1FkckwjRzF2Ms8BAWwd0UMrrm0PdyF
\r
95 LJ/VQD/vP7jeLu3d4jj9NJdnEHYCwshbBoW1XX0xpO7ygoRG2cAzC0DfE8Qfy2rN
\r
96 0UJCvfAep+ufZSunucM628pRNoqvu+MnJHDVI94leXFHyWda2VmvBbIJJwCRcNBi
\r
97 m61oWIBu+l28wZNIRqQeM8Cnwmf+Ty9p4IzyBdHSt0XotNcr9Ha1EP6Jx6n0+KHg
\r
98 35ZobBGeW683SD2rJHm4431DZ1V4dzfIt8YnUaYF9NriuC0VkK6QBHROUm/t3coy
\r
99 yJ21PBGOFHfwuZa4ob0HJ60GZyZCePRsy8fLHnkRC06qk1aI4qq2wNs1Ymyxhl4d
\r
100 ulEvwv5u13UwI3CBtf0cOhqMtjUOYkm+U/XsXHJZ+OJooP1bF9t6pSw9rq9jR+DU
\r
101 dHKeKddxG+A9JdD9jRpvCDkcD1pWRW2w8Z5Zi02gHzM/GM1HC05JyQH/GhJq08ME
\r
102 Ay+PxyXTQDgeFVWdczZ4hyJ/sqGOFx+9OZ2wOIkZPtKy+MCtoy4ajsQZxD1CSaB7
\r
103 ey8/CFkiffnHttgcdVS/UmPxRaF9N92e2PbPCnSjiND4zRszG1OxHCd9+FubqNpA
\r
104 UiWSFQHfQrtbsS78AFqD
\r
106 -----END PGP SIGNATURE-----
\r