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 0FA3E431FD4
\r
6 for <notmuch@notmuchmail.org>; Sun, 17 Nov 2013 12:51:56 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=1.313 tagged_above=-999 required=5
\r
12 tests=[URI_HEX=1.313] 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 4VC+OMed61WV for <notmuch@notmuchmail.org>;
\r
16 Sun, 17 Nov 2013 12:51:48 -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 6A002431FAF
\r
19 for <notmuch@notmuchmail.org>; Sun, 17 Nov 2013 12:51:48 -0800 (PST)
\r
20 Received: by idaaas.com (Postfix, from userid 1001)
\r
21 id 6C2BE563A7; Sun, 17 Nov 2013 21:51:43 +0100 (CET)
\r
22 Content-Type: text/plain; charset="utf-8"
\r
24 Content-Transfer-Encoding: quoted-printable
\r
25 From: apmanine@idaaas.com
\r
26 User-Agent: alot/0.3.5
\r
27 To: Patrick Totzke <patricktotzke@gmail.com>,
\r
28 "Jameson Graef Rollins" <jrollins@finestructure.net>,
\r
29 notmuch@notmuchmail.org
\r
30 References: <20131112142742.8912.57064@localhost.localdomain>
\r
31 <87eh6gxeex.fsf@servo.finestructure.net>
\r
32 <20131117185754.31928.60825@brick>
\r
33 In-Reply-To: <20131117185754.31928.60825@brick>
\r
34 Message-ID: <20131117205143.15503.76684@localhost.localdomain>
\r
35 Subject: Re: alot: can't read sent emails, after encryption
\r
36 Date: Sun, 17 Nov 2013 21:51:43 +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: Sun, 17 Nov 2013 20:51:56 -0000
\r
51 Quoting Patrick Totzke (2013-11-17 19:57:54)
\r
52 > Quoting Jameson Graef Rollins (2013-11-16 21:47:02)
\r
53 > > On Tue, Nov 12 2013, apmanine@idaaas.com wrote:
\r
54 > > > I have recently switched to notmuch. Thank you for it!
\r
55 > > > I'm using "alot" as a frontend (thank you for it, too!). Everything
\r
56 > > > works smoothly, apart from one problem: with alot, I can't figure out=
\r
58 > > > to read encrypted emails I previously sent: they appear to be encrypt=
\r
60 > > > using the addressee's key.
\r
62 > > > Is there some way to store encrypted sent emails with my own public g=
\r
67 > > What you really want is to tell gpg to always encrypt messages to your
\r
68 > > personal key as well, which will always make them viewable by you. This
\r
69 > > way you don't have to worry about saving unencrypted versions of the
\r
70 > > message to disk, or there being two distinct versions of the message
\r
71 > > (one encrypted to the recipient and a different one encrypted to you).
\r
74 > > See the "encrypt-to" gpg option [0].
\r
80 > > [0] http://www.gnupg.org/documentation/manuals/gnupg-devel/GPG-Key-rela=
\r
84 > Is this how notmuch emacs does it? I mean, is there some option to tell
\r
85 > emacs to always call gpg with --encrypt-to=3Dme ?
\r
86 > I wonder if I need to change alot in any way or if one can simply globall=
\r
88 > gnupg.. alot does not call the gpg binary but uses pygpgme.
\r
92 I didn't have time to test yet, but this thread suggest that
\r
93 the --encrypt-to option is the recommended way for notmuch-emacs:
\r
95 > 2. This is not necessarily related to notmuch itself but rather to
\r
96 > message-mode: Why are the mails that are fcc'ed to my sent-folder
\r
97 > encrypted with the recipient's key (instead of my own or simply no
\r
98 > key)? I.e. why can't I read my own mails? Is there any way to make
\r
102 What about setting this on the gpg level with the "encrypt-to" option? =
\r
105 source: http://notmuch.198994.n3.nabble.com/Inline-encryption-encryption-fa=
\r
106 ilure-when-storing-sent-mails-td4028572.html
\r