Return-Path: <patricktotzke@gmail.com>
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 E970A431FAF
	for <notmuch@notmuchmail.org>; Mon, 18 Nov 2013 01:29:24 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
X-Spam-Flag: NO
X-Spam-Score: -0.799
X-Spam-Level: 
X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5
	tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
	FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 5Xglh7e8IbZS for <notmuch@notmuchmail.org>;
	Mon, 18 Nov 2013 01:29:17 -0800 (PST)
Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com
 [74.125.82.43])	(using TLSv1 with cipher RC4-SHA (128/128 bits))	(No client
 certificate requested)	by olra.theworths.org (Postfix) with ESMTPS id
 86AB8431FAE	for <notmuch@notmuchmail.org>; Mon, 18 Nov 2013 01:29:17 -0800
 (PST)
Received: by mail-wg0-f43.google.com with SMTP id n12so5775819wgh.34
	for <notmuch@notmuchmail.org>; Mon, 18 Nov 2013 01:29:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=content-type:mime-version:content-disposition:from:user-agent:to
	:references:in-reply-to:message-id:subject:date;
	bh=9QRZJCNjl6ZAimxKRCkYXUVa1+phXjWRItj8mnvEu4o=;
	b=Ji5//0zgjMZnOsb2MlL1zghnrSV1nkn0e9UHSNYpWQ3D2AwR9QD38nYR0mi/HXtWNo
	hGE8fDSZbFPqbvGcBjiHW2vkBlgp/IKWOEx3Ac5nAGYrTGvjVqj7kBE6UppqTMOp7Dw2
	VKy8hwhz1G5HWK6x7om3cYzF9ncu/UMNTiF7etr6PuHErvzAzaOmx3WTNc8uTk8yiIgZ
	ZhHWyp3Dvg5vR+KHJRRrQeOynkG7diooVHF/ocCLHj9xa9mqHHMonkDCoVUrRbznjg0l
	c48maBSxCAVbgkUZnodpDeCsDR451T1s32DhS5u+y/I/v0nqdnjxg/VJ/hg8vcqdjNvU
	CYJw==
X-Received: by 10.194.84.72 with SMTP id w8mr268011wjy.55.1384766479162;
	Mon, 18 Nov 2013 01:21:19 -0800 (PST)
Received: from localhost (dhcp-90-208.inf.ed.ac.uk. [129.215.90.208])
	by mx.google.com with ESMTPSA id pi6sm22219457wic.3.2013.11.18.01.21.17
	for <multiple recipients>
	(version=TLSv1.2 cipher=RC4-SHA bits=128/128);
	Mon, 18 Nov 2013 01:21:18 -0800 (PST)
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg="pgp-sha1"; boundary="===============8809355610974892594=="
MIME-Version: 1.0
Content-Disposition: inline
From: Patrick Totzke <patricktotzke@gmail.com>
User-Agent: alot/0.3.5
To: Alain-Pierre Manine <apmanine@idaaas.com>,
	"Jameson Graef Rollins" <jrollins@finestructure.net>,
	notmuch@notmuchmail.org
References: <20131112142742.8912.57064@localhost.localdomain>
	<87eh6gxeex.fsf@servo.finestructure.net>
	<20131117185754.31928.60825@brick>
	<87pppy95lu.fsf@servo.finestructure.net>
	<20131118073833.19524.14797@localhost.localdomain>
In-Reply-To: <20131118073833.19524.14797@localhost.localdomain>
Message-ID: <20131118092114.23066.92699@brick>
Subject: Re: alot: can't read sent emails, after encryption
Date: Mon, 18 Nov 2013 10:21:14 +0100
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Use and development of the notmuch mail system."
	<notmuch.notmuchmail.org>
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2013 09:29:25 -0000

--===============8809355610974892594==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Quoting Alain-Pierre Manine (2013-11-18 08:38:33)
> Quoting Jameson Graef Rollins (2013-11-17 20:43:25)
> > On Sun, Nov 17 2013, Patrick Totzke <patricktotzke@gmail.com> 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 =
out how
> > >> > to read encrypted emails I previously sent: they appear to be encr=
ypted
> > >> > using the addressee's key.
> > >> >
> > >> > Is there some way to store encrypted sent emails with my own publi=
c gpg
> > >> > key?
> > >> =

> > >> What you really want is to tell gpg to always encrypt messages to yo=
ur
> > >> personal key as well, which will always make them viewable by you.  =
This
> > >> 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-r=
elated-Options.html
> > >
> > > Is this how notmuch emacs does it? I mean, is there some option to te=
ll
> > > 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 glo=
bally 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 <keyid>
> > =

> > line to your ~/.gnupg/gpg.conf, where <keyid> 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.


Excelent, thanks Jamie.
I wasn't aware of this setting and assumed that the stuff in the
gnupg config file only applies to gpg itself and not, as in alot,
for calls through the gpgme library.
Thanks for testing this Alain-Pierre.
/p

--===============8809355610974892594==
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Description: signature
Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iEYEABECAAYFAlKJ3AoACgkQlDQDZ9fWxarMFwCgrEIKbnQde342HL8qfW2qMqq/
1eoAnjJ+zgdBHpDjMHPT2CSdkJFNa+pD
=k278
-----END PGP SIGNATURE-----

--===============8809355610974892594==--