Re: (emacs) Parsing problems replying to encrypted html

diff --git a/3b/9c1952f72b4226314b9fde7200eb8a592cac1c b/3b/9c1952f72b4226314b9fde7200eb8a592cac1c
new file mode 100644 (file)
index 0000000..7563f14
--- /dev/null
+++ b/3b/9c1952f72b4226314b9fde7200eb8a592cac1c
@@ -0,0 +1,88 @@
+Return-Path: <david@tethera.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 arlo.cworth.org (Postfix) with ESMTP id 024E36DE00E8\r
+ for <notmuch@notmuchmail.org>; Sat, 23 Jul 2016 06:40:34 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.011\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[AWL=0.000,\r
+  SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id tdTjDzjxXbD5 for <notmuch@notmuchmail.org>;\r
+ Sat, 23 Jul 2016 06:40:26 -0700 (PDT)\r
+Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id 27ECF6DE00DA\r
+ for <notmuch@notmuchmail.org>; Sat, 23 Jul 2016 06:40:25 -0700 (PDT)\r
+Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2)\r
+ (envelope-from <david@tethera.net>)\r
+ id 1bQxAV-0006JX-Tu; Sat, 23 Jul 2016 09:40:39 -0400\r
+Received: (nullmailer pid 6587 invoked by uid 1000);\r
+ Sat, 23 Jul 2016 13:40:17 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: Matthew Lear <matt@bubblegen.co.uk>\r
+Cc: Matthew Lear <matt@bubblegen.co.uk>, notmuch@notmuchmail.org,\r
+ David Edmondson <dme@dme.org>, Mark Walters <markwalters1009@gmail.com>\r
+Subject: Re: (emacs) Parsing problems replying to encrypted html\r
+In-Reply-To: <3d06c4bede0643230bea93cb5d58ca6d.squirrel@webmail.plus.net>\r
+References: <f50e07855e9bbbdd780ef925d8e2d879.squirrel@webmail.plus.net>\r
+ <m2a8miwc6x.fsf@dme.org>\r
+ <c4ff9f2c141441be10b1cb4b1e0300a7.squirrel@webmail.plus.net>\r
+ <56DD48B3.90604@bubblegen.co.uk> <87mvqatr6y.fsf@zancas.localnet>\r
+ <87h9gigfyz.fsf@bubblegen.co.uk> <87pov58b9y.fsf@zancas.localnet>\r
+ <m260wxkvf3.fsf@guru.guru-group.fi> <87wpp76ctq.fsf@zancas.localnet>\r
+ <m2shzvrccn.fsf@dme.org> <87h9fm315q.fsf@bubblegen.co.uk>\r
+ <87oa9timv7.fsf@zancas.localnet>\r
+ <575b60a1d39a1ecc7d06e5c0d625be61.squirrel@webmail.plus.net>\r
+ <87bn5tjw5e.fsf@tesseract.cs.unb.ca>\r
+ <5ed42cd5aafdc045b5d9e1b918d10748.squirrel@webmail.plus.net>\r
+ <87mvpdgp38.fsf@bubblegen.co.uk> <87lh4wj4kq.fsf@zancas.localnet>\r
+ <3d06c4bede0643230bea93cb5d58ca6d.squirrel@webmail.plus.net>\r
+User-Agent: Notmuch/0.22+58~g3a45d29 (https://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Sat, 23 Jul 2016 09:40:17 -0400\r
+Message-ID: <878tws4gn2.fsf@maritornes.cs.unb.ca>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://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: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 23 Jul 2016 13:40:34 -0000\r
+\r
+Matthew Lear <matt@bubblegen.co.uk> writes:\r
+\r
+> I could have sworn that I replied to this thread months ago but can't find\r
+> a record it in the archives... I think I also missed David E's reply to\r
+> yours mentioning the patch from id:1459708823-1852-1-git-send-email-dme at\r
+> dme.org, so I'm following up...\r
+>\r
+> With David E's patch, the decryption problem I reported is resolved.\r
+> However, I notice that this change hasn't yet been committed / pushed. Is\r
+> there a particular reason for this?\r
+\r
+I guess lack of feedback as to whether the patch actually fixes the problem.\r
+\r
+> I'm currently maintaining a version of this patch compatible with the\r
+> current master which makes this change to notmuch-mua.el\r
+> notmuch-mua-reply() by adding (notmuch-show-process-crypto process-crypto)\r
+> before doing the show. I've attached that patch here.\r
+>\r
+> I just wondered if we were going to see this pushed to master any time soon?\r
+\r
+Perhaps you or dme could send an updated version of the patch to the\r
+list, as git-format-patch output (i.e. with a commit message and other\r
+metadata).\r
+\r
+d\r