--- /dev/null
+Return-Path: <patricktotzke@gmail.com>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id E970A431FAF\r
+ for <notmuch@notmuchmail.org>; Mon, 18 Nov 2013 01:29:24 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.799\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5\r
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+ FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id 5Xglh7e8IbZS for <notmuch@notmuchmail.org>;\r
+ Mon, 18 Nov 2013 01:29:17 -0800 (PST)\r
+Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com\r
+ [74.125.82.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client\r
+ certificate requested) by olra.theworths.org (Postfix) with ESMTPS id\r
+ 86AB8431FAE for <notmuch@notmuchmail.org>; Mon, 18 Nov 2013 01:29:17 -0800\r
+ (PST)\r
+Received: by mail-wg0-f43.google.com with SMTP id n12so5775819wgh.34\r
+ for <notmuch@notmuchmail.org>; Mon, 18 Nov 2013 01:29:15 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+ h=content-type:mime-version:content-disposition:from:user-agent:to\r
+ :references:in-reply-to:message-id:subject:date;\r
+ bh=9QRZJCNjl6ZAimxKRCkYXUVa1+phXjWRItj8mnvEu4o=;\r
+ b=Ji5//0zgjMZnOsb2MlL1zghnrSV1nkn0e9UHSNYpWQ3D2AwR9QD38nYR0mi/HXtWNo\r
+ hGE8fDSZbFPqbvGcBjiHW2vkBlgp/IKWOEx3Ac5nAGYrTGvjVqj7kBE6UppqTMOp7Dw2\r
+ VKy8hwhz1G5HWK6x7om3cYzF9ncu/UMNTiF7etr6PuHErvzAzaOmx3WTNc8uTk8yiIgZ\r
+ ZhHWyp3Dvg5vR+KHJRRrQeOynkG7diooVHF/ocCLHj9xa9mqHHMonkDCoVUrRbznjg0l\r
+ c48maBSxCAVbgkUZnodpDeCsDR451T1s32DhS5u+y/I/v0nqdnjxg/VJ/hg8vcqdjNvU\r
+ CYJw==\r
+X-Received: by 10.194.84.72 with SMTP id w8mr268011wjy.55.1384766479162;\r
+ Mon, 18 Nov 2013 01:21:19 -0800 (PST)\r
+Received: from localhost (dhcp-90-208.inf.ed.ac.uk. [129.215.90.208])\r
+ by mx.google.com with ESMTPSA id pi6sm22219457wic.3.2013.11.18.01.21.17\r
+ for <multiple recipients>\r
+ (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+ Mon, 18 Nov 2013 01:21:18 -0800 (PST)\r
+Content-Type: multipart/signed; protocol="application/pgp-signature";\r
+ micalg="pgp-sha1"; boundary="===============8809355610974892594=="\r
+MIME-Version: 1.0\r
+Content-Disposition: inline\r
+From: Patrick Totzke <patricktotzke@gmail.com>\r
+User-Agent: alot/0.3.5\r
+To: Alain-Pierre Manine <apmanine@idaaas.com>,\r
+ "Jameson Graef Rollins" <jrollins@finestructure.net>,\r
+ notmuch@notmuchmail.org\r
+References: <20131112142742.8912.57064@localhost.localdomain>\r
+ <87eh6gxeex.fsf@servo.finestructure.net>\r
+ <20131117185754.31928.60825@brick>\r
+ <87pppy95lu.fsf@servo.finestructure.net>\r
+ <20131118073833.19524.14797@localhost.localdomain>\r
+In-Reply-To: <20131118073833.19524.14797@localhost.localdomain>\r
+Message-ID: <20131118092114.23066.92699@brick>\r
+Subject: Re: alot: can't read sent emails, after encryption\r
+Date: Mon, 18 Nov 2013 10:21:14 +0100\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 18 Nov 2013 09:29:25 -0000\r
+\r
+--===============8809355610974892594==\r
+Content-Type: text/plain; charset="utf-8"\r
+MIME-Version: 1.0\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+Quoting Alain-Pierre Manine (2013-11-18 08:38:33)\r
+> Quoting Jameson Graef Rollins (2013-11-17 20:43:25)\r
+> > On Sun, Nov 17 2013, Patrick Totzke <patricktotzke@gmail.com> wrote:\r
+> > > Quoting Jameson Graef Rollins (2013-11-16 21:47:02)\r
+> > >> On Tue, Nov 12 2013, apmanine@idaaas.com wrote:\r
+> > >> > I have recently switched to notmuch. Thank you for it!\r
+> > >> > I'm using "alot" as a frontend (thank you for it, too!). Everything\r
+> > >> > works smoothly, apart from one problem: with alot, I can't figure =\r
+out how\r
+> > >> > to read encrypted emails I previously sent: they appear to be encr=\r
+ypted\r
+> > >> > using the addressee's key.\r
+> > >> >\r
+> > >> > Is there some way to store encrypted sent emails with my own publi=\r
+c gpg\r
+> > >> > key?\r
+> > >> =\r
+\r
+> > >> What you really want is to tell gpg to always encrypt messages to yo=\r
+ur\r
+> > >> personal key as well, which will always make them viewable by you. =\r
+This\r
+> > >> way you don't have to worry about saving unencrypted versions of the\r
+> > >> message to disk, or there being two distinct versions of the message\r
+> > >> (one encrypted to the recipient and a different one encrypted to you=\r
+).\r
+> > >> =\r
+\r
+> > >> See the "encrypt-to" gpg option [0].\r
+> > >> =\r
+\r
+> > >> jamie.\r
+> > >> =\r
+\r
+> > >> [0] http://www.gnupg.org/documentation/manuals/gnupg-devel/GPG-Key-r=\r
+elated-Options.html\r
+> > >\r
+> > > Is this how notmuch emacs does it? I mean, is there some option to te=\r
+ll\r
+> > > emacs to always call gpg with --encrypt-to=3Dme ?\r
+> > > I wonder if I need to change alot in any way or if one can simply glo=\r
+bally configure\r
+> > > gnupg.. alot does not call the gpg binary but uses pygpgme.\r
+> > =\r
+\r
+> > You do not need to change alot, just notmuch emacs also doesn't need to\r
+> > do anything special to allow for this. Just add an\r
+> > =\r
+\r
+> > encrypt-to <keyid>\r
+> > =\r
+\r
+> > line to your ~/.gnupg/gpg.conf, where <keyid> is your personal keyid.\r
+> > Then all encrypted data is also encrypted to your personal key, making\r
+> > it always viewable by you as well. Then you can just open your\r
+> > encrypted sent mail as you would any other encrypted mail.\r
+> > =\r
+\r
+> > jamie.\r
+> =\r
+\r
+> It's working! Thanks for the explanations.\r
+\r
+\r
+Excelent, thanks Jamie.\r
+I wasn't aware of this setting and assumed that the stuff in the\r
+gnupg config file only applies to gpg itself and not, as in alot,\r
+for calls through the gpgme library.\r
+Thanks for testing this Alain-Pierre.\r
+/p\r
+\r
+--===============8809355610974892594==\r
+MIME-Version: 1.0\r
+Content-Transfer-Encoding: 7bit\r
+Content-Description: signature\r
+Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v2.0.20 (GNU/Linux)\r
+\r
+iEYEABECAAYFAlKJ3AoACgkQlDQDZ9fWxarMFwCgrEIKbnQde342HL8qfW2qMqq/\r
+1eoAnjJ+zgdBHpDjMHPT2CSdkJFNa+pD\r
+=k278\r
+-----END PGP SIGNATURE-----\r
+\r
+--===============8809355610974892594==--\r
projects / notmuch-archives.git / commitdiff