From ded8ea27aa284977e82e64c9fa61edff7fca5125 Mon Sep 17 00:00:00 2001 From: apmanine Date: Sun, 17 Nov 2013 21:51:43 +0100 Subject: [PATCH] Re: alot: can't read sent emails, after encryption --- 43/39b3df9def94c41f7bbc1697dfa6cf0544c011 | 108 ++++++++++++++++++++++ 1 file changed, 108 insertions(+) create mode 100644 43/39b3df9def94c41f7bbc1697dfa6cf0544c011 diff --git a/43/39b3df9def94c41f7bbc1697dfa6cf0544c011 b/43/39b3df9def94c41f7bbc1697dfa6cf0544c011 new file mode 100644 index 000000000..1859c04fd --- /dev/null +++ b/43/39b3df9def94c41f7bbc1697dfa6cf0544c011 @@ -0,0 +1,108 @@ +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 0FA3E431FD4 + for ; Sun, 17 Nov 2013 12:51:56 -0800 (PST) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: 1.313 +X-Spam-Level: * +X-Spam-Status: No, score=1.313 tagged_above=-999 required=5 + tests=[URI_HEX=1.313] 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 4VC+OMed61WV for ; + Sun, 17 Nov 2013 12:51:48 -0800 (PST) +Received: from idaaas.com (ns213396.ovh.net [188.165.221.229]) + by olra.theworths.org (Postfix) with ESMTP id 6A002431FAF + for ; Sun, 17 Nov 2013 12:51:48 -0800 (PST) +Received: by idaaas.com (Postfix, from userid 1001) + id 6C2BE563A7; Sun, 17 Nov 2013 21:51:43 +0100 (CET) +Content-Type: text/plain; charset="utf-8" +MIME-Version: 1.0 +Content-Transfer-Encoding: quoted-printable +From: apmanine@idaaas.com +User-Agent: alot/0.3.5 +To: Patrick Totzke , + "Jameson Graef Rollins" , + notmuch@notmuchmail.org +References: <20131112142742.8912.57064@localhost.localdomain> + <87eh6gxeex.fsf@servo.finestructure.net> + <20131117185754.31928.60825@brick> +In-Reply-To: <20131117185754.31928.60825@brick> +Message-ID: <20131117205143.15503.76684@localhost.localdomain> +Subject: Re: alot: can't read sent emails, after encryption +Date: Sun, 17 Nov 2013 21:51:43 +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 20:51:56 -0000 + +Quoting Patrick Totzke (2013-11-17 19:57:54) +> 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 encrypt= +ed +> > > using the addressee's key. +> > > +> > > Is there some way to store encrypted sent emails with my own public g= +pg +> > > 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-rela= +ted-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. +> cheers, +> /p + +I didn't have time to test yet, but this thread suggest that +the --encrypt-to option is the recommended way for notmuch-emacs: + + > 2. This is not necessarily related to notmuch itself but rather to + > message-mode: Why are the mails that are fcc'ed to my sent-folder + > encrypted with the recipient's key (instead of my own or simply no + > key)? I.e. why can't I read my own mails? Is there any way to make + > this work? = + + + What about setting this on the gpg level with the "encrypt-to" option? = + + +source: http://notmuch.198994.n3.nabble.com/Inline-encryption-encryption-fa= +ilure-when-storing-sent-mails-td4028572.html + +Alain-Pierre -- 2.26.2