1 Return-Path: <apmanine@idaaas.com>
\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 56FA5431FAF
\r
6 for <notmuch@notmuchmail.org>; Sun, 17 Nov 2013 23:38:44 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\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 GMxns-gygYge for <notmuch@notmuchmail.org>;
\r
16 Sun, 17 Nov 2013 23:38:35 -0800 (PST)
\r
17 Received: from idaaas.com (ns213396.ovh.net [188.165.221.229])
\r
18 by olra.theworths.org (Postfix) with ESMTP id A46AB431FAE
\r
19 for <notmuch@notmuchmail.org>; Sun, 17 Nov 2013 23:38:35 -0800 (PST)
\r
20 Received: by idaaas.com (Postfix, from userid 1001)
\r
21 id C792D563A7; Mon, 18 Nov 2013 08:38:33 +0100 (CET)
\r
22 Content-Type: text/plain; charset="utf-8"
\r
24 Content-Transfer-Encoding: quoted-printable
\r
25 From: Alain-Pierre Manine <apmanine@idaaas.com>
\r
26 User-Agent: alot/0.3.5
\r
27 To: Jameson Graef Rollins <jrollins@finestructure.net>,
\r
28 "Patrick Totzke" <patricktotzke@gmail.com>, notmuch@notmuchmail.org
\r
29 References: <20131112142742.8912.57064@localhost.localdomain>
\r
30 <87eh6gxeex.fsf@servo.finestructure.net>
\r
31 <20131117185754.31928.60825@brick>
\r
32 <87pppy95lu.fsf@servo.finestructure.net>
\r
33 In-Reply-To: <87pppy95lu.fsf@servo.finestructure.net>
\r
34 Message-ID: <20131118073833.19524.14797@localhost.localdomain>
\r
35 Subject: Re: alot: can't read sent emails, after encryption
\r
36 Date: Mon, 18 Nov 2013 08:38:33 +0100
\r
37 X-BeenThere: notmuch@notmuchmail.org
\r
38 X-Mailman-Version: 2.1.13
\r
40 List-Id: "Use and development of the notmuch mail system."
\r
41 <notmuch.notmuchmail.org>
\r
42 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
43 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
44 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
45 List-Post: <mailto:notmuch@notmuchmail.org>
\r
46 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
47 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
48 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
49 X-List-Received-Date: Mon, 18 Nov 2013 07:38:44 -0000
\r
51 Quoting Jameson Graef Rollins (2013-11-17 20:43:25)
\r
52 > On Sun, Nov 17 2013, Patrick Totzke <patricktotzke@gmail.com> wrote:
\r
53 > > Quoting Jameson Graef Rollins (2013-11-16 21:47:02)
\r
54 > >> On Tue, Nov 12 2013, apmanine@idaaas.com wrote:
\r
55 > >> > I have recently switched to notmuch. Thank you for it!
\r
56 > >> > I'm using "alot" as a frontend (thank you for it, too!). Everything
\r
57 > >> > works smoothly, apart from one problem: with alot, I can't figure ou=
\r
59 > >> > to read encrypted emails I previously sent: they appear to be encryp=
\r
61 > >> > using the addressee's key.
\r
63 > >> > Is there some way to store encrypted sent emails with my own public =
\r
68 > >> What you really want is to tell gpg to always encrypt messages to your
\r
69 > >> personal key as well, which will always make them viewable by you. Th=
\r
71 > >> way you don't have to worry about saving unencrypted versions of the
\r
72 > >> message to disk, or there being two distinct versions of the message
\r
73 > >> (one encrypted to the recipient and a different one encrypted to you).
\r
76 > >> See the "encrypt-to" gpg option [0].
\r
82 > >> [0] http://www.gnupg.org/documentation/manuals/gnupg-devel/GPG-Key-rel=
\r
85 > > Is this how notmuch emacs does it? I mean, is there some option to tell
\r
86 > > emacs to always call gpg with --encrypt-to=3Dme ?
\r
87 > > I wonder if I need to change alot in any way or if one can simply globa=
\r
89 > > gnupg.. alot does not call the gpg binary but uses pygpgme.
\r
92 > You do not need to change alot, just notmuch emacs also doesn't need to
\r
93 > do anything special to allow for this. Just add an
\r
96 > encrypt-to <keyid>
\r
99 > line to your ~/.gnupg/gpg.conf, where <keyid> is your personal keyid.
\r
100 > Then all encrypted data is also encrypted to your personal key, making
\r
101 > it always viewable by you as well. Then you can just open your
\r
102 > encrypted sent mail as you would any other encrypted mail.
\r
107 It's working! Thanks for the explanations.
\r