From 59790051ed7984b2a8892d07c53b72f2a6196e0e Mon Sep 17 00:00:00 2001 From: Alain-Pierre Manine Date: Mon, 18 Nov 2013 08:38:33 +0100 Subject: [PATCH] Re: alot: can't read sent emails, after encryption --- 7f/857a56c764d99124dc686a154320ab6fe0c558 | 109 ++++++++++++++++++++++ 1 file changed, 109 insertions(+) create mode 100644 7f/857a56c764d99124dc686a154320ab6fe0c558 diff --git a/7f/857a56c764d99124dc686a154320ab6fe0c558 b/7f/857a56c764d99124dc686a154320ab6fe0c558 new file mode 100644 index 000000000..b0c1bc141 --- /dev/null +++ b/7f/857a56c764d99124dc686a154320ab6fe0c558 @@ -0,0 +1,109 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id 56FA5431FAF + for ; Sun, 17 Nov 2013 23:38:44 -0800 (PST) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: 0 +X-Spam-Level: +X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] + autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id GMxns-gygYge for ; + Sun, 17 Nov 2013 23:38:35 -0800 (PST) +Received: from idaaas.com (ns213396.ovh.net [188.165.221.229]) + by olra.theworths.org (Postfix) with ESMTP id A46AB431FAE + for ; Sun, 17 Nov 2013 23:38:35 -0800 (PST) +Received: by idaaas.com (Postfix, from userid 1001) + id C792D563A7; Mon, 18 Nov 2013 08:38:33 +0100 (CET) +Content-Type: text/plain; charset="utf-8" +MIME-Version: 1.0 +Content-Transfer-Encoding: quoted-printable +From: Alain-Pierre Manine +User-Agent: alot/0.3.5 +To: Jameson Graef Rollins , + "Patrick Totzke" , notmuch@notmuchmail.org +References: <20131112142742.8912.57064@localhost.localdomain> + <87eh6gxeex.fsf@servo.finestructure.net> + <20131117185754.31928.60825@brick> + <87pppy95lu.fsf@servo.finestructure.net> +In-Reply-To: <87pppy95lu.fsf@servo.finestructure.net> +Message-ID: <20131118073833.19524.14797@localhost.localdomain> +Subject: Re: alot: can't read sent emails, after encryption +Date: Mon, 18 Nov 2013 08:38:33 +0100 +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +Precedence: list +List-Id: "Use and development of the notmuch mail system." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Mon, 18 Nov 2013 07:38:44 -0000 + +Quoting Jameson Graef Rollins (2013-11-17 20:43:25) +> On Sun, Nov 17 2013, Patrick Totzke wrote: +> > Quoting Jameson Graef Rollins (2013-11-16 21:47:02) +> >> On Tue, Nov 12 2013, apmanine@idaaas.com wrote: +> >> > I have recently switched to notmuch. Thank you for it! +> >> > I'm using "alot" as a frontend (thank you for it, too!). Everything +> >> > works smoothly, apart from one problem: with alot, I can't figure ou= +t how +> >> > to read encrypted emails I previously sent: they appear to be encryp= +ted +> >> > using the addressee's key. +> >> > +> >> > Is there some way to store encrypted sent emails with my own public = +gpg +> >> > key? +> >> = + +> >> What you really want is to tell gpg to always encrypt messages to your +> >> personal key as well, which will always make them viewable by you. Th= +is +> >> way you don't have to worry about saving unencrypted versions of the +> >> message to disk, or there being two distinct versions of the message +> >> (one encrypted to the recipient and a different one encrypted to you). +> >> = + +> >> See the "encrypt-to" gpg option [0]. +> >> = + +> >> jamie. +> >> = + +> >> [0] http://www.gnupg.org/documentation/manuals/gnupg-devel/GPG-Key-rel= +ated-Options.html +> > +> > Is this how notmuch emacs does it? I mean, is there some option to tell +> > emacs to always call gpg with --encrypt-to=3Dme ? +> > I wonder if I need to change alot in any way or if one can simply globa= +lly configure +> > gnupg.. alot does not call the gpg binary but uses pygpgme. +> = + +> You do not need to change alot, just notmuch emacs also doesn't need to +> do anything special to allow for this. Just add an +> = + +> encrypt-to +> = + +> line to your ~/.gnupg/gpg.conf, where is your personal keyid. +> Then all encrypted data is also encrypted to your personal key, making +> it always viewable by you as well. Then you can just open your +> encrypted sent mail as you would any other encrypted mail. +> = + +> jamie. + +It's working! Thanks for the explanations. + + -- 2.26.2