From 980c9c7d7cd3390d7736ae75353f6f7c80dbafd8 Mon Sep 17 00:00:00 2001 From: Patrick Totzke Date: Sun, 17 Nov 2013 19:57:54 +0100 Subject: [PATCH] Re: alot: can't read sent emails, after encryption --- 32/497bde78ff6a6b2b35fca5fae71499e682d74e | 126 ++++++++++++++++++++++ 1 file changed, 126 insertions(+) create mode 100644 32/497bde78ff6a6b2b35fca5fae71499e682d74e diff --git a/32/497bde78ff6a6b2b35fca5fae71499e682d74e b/32/497bde78ff6a6b2b35fca5fae71499e682d74e new file mode 100644 index 000000000..22dcafc36 --- /dev/null +++ b/32/497bde78ff6a6b2b35fca5fae71499e682d74e @@ -0,0 +1,126 @@ +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 0B3CC431FD4 + for ; Sun, 17 Nov 2013 10:58:14 -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 zr6TZb5hkXmj for ; + Sun, 17 Nov 2013 10:58:05 -0800 (PST) +Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com + [209.85.212.182]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 612B1431FAF + for ; Sun, 17 Nov 2013 10:58:05 -0800 (PST) +Received: by mail-wi0-f182.google.com with SMTP id en1so1093423wid.15 + for ; Sun, 17 Nov 2013 10:58:02 -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=7RpcnSMbVXpJmHiAIdDoDt1GLbm6avB8KtVVGH/hseM=; + b=btT7bptOrHOnUyCYG4NnX9DZbuwj0wWqrAd8g2wkYy7QfE1PSROQY2M51SqBQoA/6P + udpEf32YZIm6oh5fv7GVAxh7bO7JumH+VJaRapMaNEuurSBciP/fV4tJQO2VFIi82Ry1 + OIp32MQ9ormophGdXhUGKF4YZTNWRe8NV77JuGIvZ6JWWyHrFoHrF3Rak8JDfSCrCCt0 + FaKcdWvZjDceZSCHXf5azBcdO+E4++YvaXFOpa8Lt0jD2FtDhbr+otq2GmxV2D0xGgLD + 7Y/k6tKwGWqr/w8Ax/V68PWAVL/yEytVJDA/RsJvIVVarsxml1KYtNdWheDKpJnOx4QQ + mcLQ== +X-Received: by 10.194.219.1 with SMTP id pk1mr13725055wjc.36.1384714682780; + Sun, 17 Nov 2013 10:58:02 -0800 (PST) +Received: from localhost ([129.215.125.174]) + by mx.google.com with ESMTPSA id dj8sm16640291wid.2.2013.11.17.10.57.59 + for + (version=TLSv1.2 cipher=RC4-SHA bits=128/128); + Sun, 17 Nov 2013 10:58:01 -0800 (PST) +Content-Type: multipart/signed; protocol="application/pgp-signature"; + micalg="pgp-sha1"; boundary="===============2090883252728387735==" +MIME-Version: 1.0 +Content-Disposition: inline +From: Patrick Totzke +User-Agent: alot/0.3.5 +To: Jameson Graef Rollins , apmanine@idaaas.com, + notmuch@notmuchmail.org +References: <20131112142742.8912.57064@localhost.localdomain> + <87eh6gxeex.fsf@servo.finestructure.net> +In-Reply-To: <87eh6gxeex.fsf@servo.finestructure.net> +Message-ID: <20131117185754.31928.60825@brick> +Subject: Re: alot: can't read sent emails, after encryption +Date: Sun, 17 Nov 2013 19:57:54 +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: Sun, 17 Nov 2013 18:58:14 -0000 + +--===============2090883252728387735== +Content-Type: text/plain; charset="utf-8" +MIME-Version: 1.0 +Content-Transfer-Encoding: quoted-printable + +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 h= +ow +> > 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? +> = + +> 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). +> = + +> See the "encrypt-to" gpg option [0]. +> = + +> jamie. +> = + +> [0] http://www.gnupg.org/documentation/manuals/gnupg-devel/GPG-Key-relate= +d-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 globally = +configure +gnupg.. alot does not call the gpg binary but uses pygpgme. +cheers, +/p + +--===============2090883252728387735== +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) + +iEYEABECAAYFAlKJEbIACgkQlDQDZ9fWxaqgSACbBXSE3neeYHdQIvCetFvCpkZm +JHIAn1dO4tCmBoDQl2VPv8bBoYst0k+X +=6xSj +-----END PGP SIGNATURE----- + +--===============2090883252728387735==-- -- 2.26.2