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 461C8431FD4 for ; Sun, 17 Nov 2013 11:43:38 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -2.3 X-Spam-Level: X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3] 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 KXM7xLR6Pez9 for ; Sun, 17 Nov 2013 11:43:33 -0800 (PST) Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu [131.215.239.19]) by olra.theworths.org (Postfix) with ESMTP id 88FC4431FAF for ; Sun, 17 Nov 2013 11:43:33 -0800 (PST) Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1]) by fire-doxen-postvirus (Postfix) with ESMTP id 1F7C1328014; Sun, 17 Nov 2013 11:43:31 -0800 (PST) X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new Received: from finestructure.net (unknown [198.129.209.202]) (Authenticated sender: jrollins) by fire-doxen-submit (Postfix) with ESMTP id 2179D32800B; Sun, 17 Nov 2013 11:43:30 -0800 (PST) Received: by finestructure.net (Postfix, from userid 1000) id 32AF06008E; Sun, 17 Nov 2013 11:43:28 -0800 (PST) From: Jameson Graef Rollins To: Patrick Totzke , apmanine@idaaas.com, notmuch@notmuchmail.org Subject: Re: alot: can't read sent emails, after encryption In-Reply-To: <20131117185754.31928.60825@brick> References: <20131112142742.8912.57064@localhost.localdomain> <87eh6gxeex.fsf@servo.finestructure.net> <20131117185754.31928.60825@brick> User-Agent: Notmuch/0.16+168~gf3d6c8c (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Sun, 17 Nov 2013 11:43:25 -0800 Message-ID: <87pppy95lu.fsf@servo.finestructure.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" 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: Sun, 17 Nov 2013 19:43:38 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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 out = how >> > to read encrypted emails I previously sent: they appear to be encrypted >> > using the addressee's key. >> > >> > Is there some way to store encrypted sent emails with my own public gpg >> > key? >>=20 >> 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. 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). >>=20 >> See the "encrypt-to" gpg option [0]. >>=20 >> jamie. >>=20 >> [0] http://www.gnupg.org/documentation/manuals/gnupg-devel/GPG-Key-relat= ed-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 globall= y 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. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iQIcBAEBCAAGBQJSiRxeAAoJEO00zqvie6q8gh0P/Rvqs/eJ66tr4XqERX3RDqE/ pwUbFNxl02/s7uoE31uyppM7JR7aUbcV2pOuH6CayeU2xgtrV0j5hlHSNq6H4/zW odX1wNAQmS8c61QQNNY+lgKebvMv0rUFPPqXoxYsMJICST25+hs6rrW/mYIZ8XXd Y4RUFoqCsBDkSftDMPXDuNrePpuKElHPlAQelnOno4LagXeZK+O0C+rfUVwPZ3Dp 8aMr16o37YWdZrEhxH8Zemdr7kuYHd8HZcS+1GXY8d5/iCLuuogucLiYNst5VZfD 9z6lapnZs1oNtdkGo4P2QA8O8BSiHjVXl5xkRApZaes4MCFk5S8cX8qarjdmlNam oAQUp0P8DNSvRIpRx7a/OnpmuItfW8Ubg2HLmk2UrGZK51BLLyUtGqCEmZ1bzBv6 Jy/XGt3MkwR28KR7yUOqgg89cYWgeznkXEiGVh7oBHtDdvhpSLycDK6KsTRN6aHz 6sykU+eS3Ah45Pzp+0jCaI8HLTV6D9/E90H0Jk60sGb1eUlLWo+z1NGd71h74HEe LX0dsh1malrYYhwHBmUtn+ejOfRoEI8Sn7DEj6swyF33xcKRc2r9wOu0g1t/DS2E idqg7H8a2YtaylwplQod9ByNAm5Pvn80rUbv4EY8XrgKdzG6p7Dffl1mxNomjd4Q 6Jm+U0gv9pMiK1OAlulQ =LYcP -----END PGP SIGNATURE----- --=-=-=--