Re: alot: can't read sent emails, after encryption
authorJameson Graef Rollins <jrollins@finestructure.net>
Sat, 16 Nov 2013 20:47:02 +0000 (12:47 +1600)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:58:20 +0000 (09:58 -0800)
be/01eb93ffb5c4fba6a9c7f6334c00d449fec46b [new file with mode: 0644]

diff --git a/be/01eb93ffb5c4fba6a9c7f6334c00d449fec46b b/be/01eb93ffb5c4fba6a9c7f6334c00d449fec46b
new file mode 100644 (file)
index 0000000..330e2d8
--- /dev/null
@@ -0,0 +1,102 @@
+Return-Path: <jrollins@finestructure.net>\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 15E00429E32\r
+       for <notmuch@notmuchmail.org>; Sat, 16 Nov 2013 12:47:15 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.3\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3] 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 0Xj9d01gOU3c for <notmuch@notmuchmail.org>;\r
+       Sat, 16 Nov 2013 12:47:07 -0800 (PST)\r
+Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu\r
+       [131.215.239.19])\r
+       by olra.theworths.org (Postfix) with ESMTP id 35F34429E30\r
+       for <notmuch@notmuchmail.org>; Sat, 16 Nov 2013 12:47:07 -0800 (PST)\r
+Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])\r
+       by fire-doxen-postvirus (Postfix) with ESMTP id C90C22E50748;\r
+       Sat, 16 Nov 2013 12:47:06 -0800 (PST)\r
+X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new\r
+Received: from finestructure.net (unknown [198.129.209.202])\r
+       (Authenticated sender: jrollins)\r
+       by fire-doxen-submit (Postfix) with ESMTP id A49AB2E5063F;\r
+       Sat, 16 Nov 2013 12:47:05 -0800 (PST)\r
+Received: by finestructure.net (Postfix, from userid 1000)\r
+       id 2E3EB60080; Sat, 16 Nov 2013 12:47:05 -0800 (PST)\r
+From: Jameson Graef Rollins <jrollins@finestructure.net>\r
+To: apmanine@idaaas.com, notmuch@notmuchmail.org\r
+Subject: Re: alot: can't read sent emails, after encryption\r
+In-Reply-To: <20131112142742.8912.57064@localhost.localdomain>\r
+References: <20131112142742.8912.57064@localhost.localdomain>\r
+User-Agent: Notmuch/0.16+120~gfd733a4 (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Sat, 16 Nov 2013 12:47:02 -0800\r
+Message-ID: <87eh6gxeex.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha256; protocol="application/pgp-signature"\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: Sat, 16 Nov 2013 20:47:15 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+\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 out how\r
+> to read encrypted emails I previously sent: they appear to be encrypted\r
+> using the addressee's key.\r
+>\r
+> Is there some way to store encrypted sent emails with my own public gpg\r
+> key?\r
+\r
+What you really want is to tell gpg to always encrypt messages to your\r
+personal key as well, which will always make them viewable by you.  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
+See the "encrypt-to" gpg option [0].\r
+\r
+jamie.\r
+\r
+[0] http://www.gnupg.org/documentation/manuals/gnupg-devel/GPG-Key-related-Options.html\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.15 (GNU/Linux)\r
+\r
+iQIcBAEBCAAGBQJSh9nHAAoJEO00zqvie6q8g14P/Roklgd9rh9a7iNnz02sRONm\r
+fOiKHVMz9tdAkJCIJePYebxYtbcsYIZXjAck91uIcw6L4/iP8xZHdn6Cx/WGk4lg\r
+oiwjvu9xhpkuCoF0dZkxJd3BPbUbE34RF9pRq1Tyj9tf9XdH3wJ+Q6R8+toTlWwN\r
+p3feVUQVn1rnKwfP2v0fA+c2sZC5X/EEeat2OkTs4aq+ffNxdpkIRfqUxiFMQOOu\r
+sGu945tBaoF3eGEz8uYYHu94cQC1fWqhtXONMqGP4CQTpuETdJzm/QeMsdSfijyz\r
+6nkF5O26YZPz+nNMRienvBCTqb1ZWQzHj82k6avYOgVLNuIJxEKpQ2O/DeRbbtES\r
+jvon3kIqAGe58egEqAnMTP3W+qSN6y8xVuT71IlQOzM4dwTq9Wsj+D4n2QR5K0Ti\r
+w7Zs7FP6Vw93gYSgAuPgOKoxECtcvLEJYrSTAqxrjrvQi+EJ/jrWfy7ifihAwfuK\r
+CQySRRFV3m0+zXGLE4Mz3j7AqlvU0sdnFMHLURP749NZMDp8Aiaxf/+L0gXwCY06\r
+7UAjTbZyVWXG9D/Vc6Wq/ZRz2asc3xJA/lwaAyOoLUwTlxmgNRkwy1DbGfHDNzWL\r
+B5ctV07PDwucFtIqPVMbYJ0WNPtR/Jkn1ZFs7UadclmeQFpbBPbrP3g4lMAmH7Pp\r
+FCh0vp+4OhSGZA/CVRvg\r
+=6lPE\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r