Re: alot: can't read sent emails, after encryption

diff --git a/2f/16654b6079646c144afaa19eb3eb80ad95a7dc b/2f/16654b6079646c144afaa19eb3eb80ad95a7dc
new file mode 100644 (file)
index 0000000..027bf71
--- /dev/null
+++ b/2f/16654b6079646c144afaa19eb3eb80ad95a7dc
@@ -0,0 +1,121 @@
+Return-Path: <meskio@sindominio.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 591A0431FD7\r
+       for <notmuch@notmuchmail.org>; Tue, 12 Nov 2013 15:01:32 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       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 1o7m9uQj3l9Q for <notmuch@notmuchmail.org>;\r
+       Tue, 12 Nov 2013 15:01:28 -0800 (PST)\r
+Received: from eternauta.sindominio.net (eternauta.sindominio.net\r
+       [213.27.140.73])\r
+       (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 234D9431FCF\r
+       for <notmuch@notmuchmail.org>; Tue, 12 Nov 2013 15:01:28 -0800 (PST)\r
+Received: from localhost (localhost.localdomain [127.0.0.1])\r
+       by lesnaus.sindominio.net (Postfix) with ESMTP id 88FEC13F9E4;\r
+       Wed, 13 Nov 2013 00:01:25 +0100 (CET)\r
+Received: from eternauta.sindominio.net ([127.0.0.1])\r
+       by localhost (lesnaus.sindominio.net [127.0.0.1]) (amavisd-new,\r
+       port 10024)\r
+       with ESMTP id TRvUGlLn2_vc; Wed, 13 Nov 2013 00:01:25 +0100 (CET)\r
+Received: from localhost (172-198-28-81.ftth.cust.kwaoo.net [81.28.198.172])\r
+       (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by lesnaus.sindominio.net (Postfix) with ESMTPSA id 03AB813F9D3;\r
+       Wed, 13 Nov 2013 00:01:23 +0100 (CET)\r
+Content-Type: multipart/signed; protocol="application/pgp-signature";\r
+       micalg="pgp-sha512"; boundary="===============2620059341096638250=="\r
+MIME-Version: 1.0\r
+Content-Disposition: inline\r
+From: Ruben Pollan <meskio@sindominio.net>\r
+User-Agent: alot/0.3.5\r
+To: apmanine@idaaas.com,  notmuch@notmuchmail.org\r
+References: <20131112142742.8912.57064@localhost.localdomain>\r
+In-Reply-To: <20131112142742.8912.57064@localhost.localdomain>\r
+Message-ID: <20131112230121.7127.72318@hermes>\r
+Subject: Re: alot: can't read sent emails, after encryption\r
+Date: Wed, 13 Nov 2013 00:01:21 +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: Tue, 12 Nov 2013 23:01:32 -0000\r
+\r
+--===============2620059341096638250==\r
+Content-Type: text/plain; charset="utf-8"\r
+MIME-Version: 1.0\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+Quoting apmanine@idaaas.com (2013-11-12 15:27:42)\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
+\r
+> Is there some way to store encrypted sent emails with my own public gpg\r
+> key?\r
+\r
+Same problem here, I think what is stored is the email that was send. It wi=\r
+ll be =\r
+\r
+great if alot stores it as you say with your own public gpg key.\r
+\r
+I think we should open an issue about in the alot github tracker:\r
+https://github.com/pazz/alot/issues\r
+Can you do it?\r
+\r
+\r
+-- =\r
+\r
+Ruben Pollan  | http://meskio.net/\r
+-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=\r
+=3D-=3D-=3D-=3D-=3D-\r
+ My contact info: http://meskio.net/crypto.txt\r
+-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=\r
+=3D-=3D-=3D-=3D-=3D-\r
+Nos vamos a Croatan.\r
+\r
+--===============2620059341096638250==\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.22 (GNU/Linux)\r
+\r
+iQIcBAABCgAGBQJSgrNBAAoJEMcysdHCj04vAVMP/1fkY5du8Aw4MgOMRx3OJdb6\r
+zsCq2kfc909VOANixxJW3co8QhjHZgh8cUKGAZIdhJ2suQmsnOV2XxAklcnF851u\r
+I87IK+LBdUQ4M1XF1PyeBS+EvEiVNzdHmCGjKwT3UFl8Ph2kDfn5Jwt7DcWhfHok\r
+PYkjUgnrF+ujBw2+P7g5MsCmSU4Uf0A6OVNGW1eKmUxgcqoYummr71jQ8BZHApy8\r
+IGRabtyPZWbkRF4MVAPxc2L66tteZtImfRnbt1Z5pJNfH7SYEembekjCs3MIOx0y\r
+hxuxs5lLA7UzggQrXhjjKCQb7ri+1LfyTr6hGBdl9C5P6pWPOGLG8LryqiexJcl9\r
+yekf/7uY7QRxcVxsxQlWX2NFojj/4WQCJRHxMeMcjTJEjyo0F7ndy++KnqTY+22H\r
+HhAMPc/r3gpzs2UJz4WENxngQ+6/iSiO++9yB84OGrP9oAWg4QgYjNuLSGcTkqsw\r
+d9K5vMfBis6NnWLv0yWFwnfCvbEif4mzBYJfsQpAyTAQ5JCLDJds7+AabMY30wV0\r
+5U8s5vHDhKiLf9DCOFLxU8MP7XVdsZJb/cPI4U/2HP+wLDFQ/7+R9Lj9ciEkcvXQ\r
+J3dok0S8zPxqo6I5K8SZh+MMFmE+4Hm4AikOuzgvF/W1oGqNs08gqyyIblsyWZbE\r
+PaFvnZE1bxe269X1/u5/\r
+=RyET\r
+-----END PGP SIGNATURE-----\r
+\r
+--===============2620059341096638250==--\r