1 Return-Path: <error4me@gmx.de>
\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 231AD429E42
\r
6 for <notmuch@notmuchmail.org>; Tue, 3 Jan 2012 16:08:39 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0.181 tagged_above=-999 required=5
\r
12 tests=[FH_FROMEML_NOTLD=0.18, FREEMAIL_FROM=0.001,
\r
13 RCVD_IN_DNSWL_NONE=-0.0001] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id 2y8qMILswpnw for <notmuch@notmuchmail.org>;
\r
17 Tue, 3 Jan 2012 16:08:38 -0800 (PST)
\r
18 Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22])
\r
19 by olra.theworths.org (Postfix) with SMTP id 2D090431FD0
\r
20 for <notmuch@notmuchmail.org>; Tue, 3 Jan 2012 16:08:38 -0800 (PST)
\r
21 Received: (qmail invoked by alias); 04 Jan 2012 00:08:36 -0000
\r
22 Received: from p54BE4204.dip.t-dialin.net (EHLO shi.workgroup) [84.190.66.4]
\r
23 by mail.gmx.net (mp062) with SMTP; 04 Jan 2012 01:08:36 +0100
\r
24 X-Authenticated: #19296480
\r
25 X-Provags-ID: V01U2FsdGVkX18DdYZxM+0DoXyFurUz4eHzEPMB2aLPbDWPaTZBFj
\r
27 Received: from grfz by shi.workgroup with local (Exim 4.77)
\r
28 (envelope-from <error4me@gmx.de>)
\r
29 id 1RiEPB-0005so-Df; Wed, 04 Jan 2012 01:08:33 +0100
\r
30 From: Gregor Zattler <Gregor@shi>
\r
31 To: Jameson Graef Rollins <jrollins@finestructure.net>,
\r
32 Gregor Zattler <telegraph@gmx.net>, Notmuch Mail <notmuch@notmuchmail.org>
\r
33 Subject: Re: Emacs: Crypto: How to get automatic encryption?
\r
34 In-Reply-To: <87fwfw8npx.fsf@servo.finestructure.net>
\r
35 References: <20120103195651.GA27869@shi.workgroup>
\r
36 <87fwfw8npx.fsf@servo.finestructure.net>
\r
37 User-Agent: Notmuch/0.10.2 (http://notmuchmail.org) Emacs/23.3.1
\r
39 Mail-Followup-To: Jameson Graef Rollins <jrollins@finestructure.net>, Gregor
\r
40 Zattler <telegraph@gmx.net>, Notmuch Mail <notmuch@notmuchmail.org>
\r
41 Date: Wed, 04 Jan 2012 01:08:33 +0100
\r
42 Message-ID: <87y5toqqgu.fsf@shi.workgroup>
\r
44 Content-Type: text/plain; charset=us-ascii
\r
46 X-Mailman-Approved-At: Wed, 11 Jan 2012 18:03:20 -0800
\r
47 X-BeenThere: notmuch@notmuchmail.org
\r
48 X-Mailman-Version: 2.1.13
\r
50 List-Id: "Use and development of the notmuch mail system."
\r
51 <notmuch.notmuchmail.org>
\r
52 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
53 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
54 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
55 List-Post: <mailto:notmuch@notmuchmail.org>
\r
56 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
57 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
58 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
59 X-List-Received-Date: Wed, 04 Jan 2012 00:08:39 -0000
\r
61 Hi Jamie, notmuch developers,
\r
62 On Tue, 03 Jan 2012 13:45:14 -0800, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
\r
63 > On Tue, 3 Jan 2012 20:56:51 +0100, Gregor Zattler <telegraph@gmx.net> wrote:
\r
64 > > I replied to a PGP/MIME signed and encrypted e-mail and was
\r
65 > > astonished to realise that my reply was sent unencrypted (and
\r
66 > > unsigened for that matter).
\r
68 > Yikes! Sorry this happened, and I hope nothing too sensitive was
\r
73 > Auto signing of outgoing mail can be enabled by the following [0]:
\r
75 > (add-hook 'message-setup-hook mml-secure-message-sign-pgpmime)
\r
77 > You can configure the message-setup-hook with the customization UI as
\r
80 I tried this and enabled mml-secure-message-encrypt-pgpmime too.
\r
81 I did a test with an address I have no public key for. I was
\r
82 informed of the fact and asked if I want to skip this key. The
\r
83 result was an email encrypted only to me (I suppose it's a
\r
84 sensible default to include the key of the sender in the list of
\r
85 key to encrypt to), so it would be unreadable for the recipient :-(
\r
87 > Unfortunately, auto encrypting of replies to encrypted emails is not yet
\r
88 > implemented. It is desperately needed, though, obviously. So this is a
\r
89 > good excuse to start a discussion about how we could achieve this.
\r
91 > It just occurs to me that a way to do this would be to have notmuch
\r
92 > reply add the appropriate mml #secure tag for encryption to the output
\r
93 > reply template, maybe with something like a --emacs option. That would
\r
94 > be pretty easy to implement, although it would obviously be very UI
\r
97 > Another possibility would be for notmuch reply to add some sort of
\r
98 > header to the reply message to indicate that the original was encrypted,
\r
99 > and then do something in emacs to try to read that header and add the
\r
100 > appropriate mml #secure tag. That would also be easy to implement in
\r
101 > the notmuch CLI, and it would be more UI agnostic, but it would require
\r
102 > a lot more elisp.
\r
104 > Or maybe we could support both?
\r
106 > Any other suggestions?
\r
108 I'm no developer; your second suggestion sounds more plausible
\r
109 me since notmuch is a frontend-agnostic mail system.
\r
111 > > Actually the message buffer in which I write replies has Auto
\r
112 > > Encryption Mode enabled, but nothing happens.
\r
114 > That's unfortunate. Can you explain exactly how you set this up, and
\r
115 > how it didn't work?
\r
117 Actually I did not set it up. I tested this again with emacs23
\r
118 -q ... It has something to do with EasyPG and therefore I assume
\r
119 it only works on the level of file encryption if the file
\r
120 associated with the buffer ends in .pgp But that's a guess.
\r
124 > It's actually usually mml that is used with message-mode to
\r
125 > sign/encrypt message, not epg.
\r
127 Thanks for your info. Actually I'm a mutt user and I customised
\r
128 mutt to opportunistically encrypt emails if I/gpg have/has public
\r
129 keys for all recipients of an email. I have no clue how to
\r
130 achieve this with Emacs.
\r