Re: (emacs) Parsing problems replying to encrypted html

diff --git a/10/284a4b691f1e9e3e34ae0eddae1e1a73d42096 b/10/284a4b691f1e9e3e34ae0eddae1e1a73d42096
new file mode 100644 (file)
index 0000000..38c721d
--- /dev/null
+++ b/10/284a4b691f1e9e3e34ae0eddae1e1a73d42096
@@ -0,0 +1,111 @@
+Return-Path: <dme@dme.org>\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 A49B56DE10C1\r
+ for <notmuch@notmuchmail.org>; Thu, 10 Mar 2016 04:24:07 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.145\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.145 tagged_above=-999 required=5\r
+ tests=[AWL=-0.078, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,\r
+ RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01,\r
+ RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.652, UNPARSEABLE_RELAY=0.001]\r
+ 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 cT2yY77NJae3 for <notmuch@notmuchmail.org>;\r
+ Thu, 10 Mar 2016 04:24:04 -0800 (PST)\r
+Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com\r
+ [74.125.82.54]) by arlo.cworth.org (Postfix) with ESMTPS id 9AC556DE0B7C for\r
+ <notmuch@notmuchmail.org>; Thu, 10 Mar 2016 04:24:03 -0800 (PST)\r
+Received: by mail-wm0-f54.google.com with SMTP id l68so26320324wml.0\r
+ for <notmuch@notmuchmail.org>; Thu, 10 Mar 2016 04:24:03 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=dme-org.20150623.gappssmtp.com; s=20150623;\r
+ h=to:cc:subject:in-reply-to:references:from:date:message-id\r
+ :mime-version; bh=CJd02nN0FhQTmmjYC460yrOCqixU4Fqe6nKD3sPhRS4=;\r
+ b=ibLFSsG8QB4wx+ic5clnDJVqK8SaZspb9+byyIZMCuzQ+9am4flPF0fnHRJB92DtV4\r
+ Fd3/XiXhh+GemS7HQSz9I8obTYpX29xm7mugvGb6wSuulVIKWjTqghywHltfDLSg8Nf0\r
+ 3ZPTjduoBPK33Tjl2pe4fr5lKSFjguzR72JeHzp3vnoPkK6A907mr9qkzXBI6m5SqmnT\r
+ Lggo5MMHojVrmwn7zzxUWGRceubrsbaqKbDoCKGb0GWN9SIWZaATdqODjIAkYFGgAGd4\r
+ HGNLxgwkthOmePZ3Vin6s3t7NdL2ofqHvcCS2Ehkzah7x6zwa5IipZEcrpEumX4WEHx1\r
+ rN9g==\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=1e100.net; s=20130820;\r
+ h=x-gm-message-state:to:cc:subject:in-reply-to:references:from:date\r
+ :message-id:mime-version;\r
+ bh=CJd02nN0FhQTmmjYC460yrOCqixU4Fqe6nKD3sPhRS4=;\r
+ b=IcwsbCLCh4yecRIkNNegzb9SLoALwFxTdpPfhEc0CPIEOMv8jUYXC2WoUENjheYvL5\r
+ 75C2ZCMpzIcxjQwE7P19SC2oZQ41tfIIJfWubUCOMUMAhHR+l+g4HHha4/kYCz5FZE7N\r
+ EjJ0ZsY/vrYrB4YIaV0OGSMZ4CnOZLx7vybp1TMlHRcgX6g9Muy1E7E042337YlMVfwy\r
+ wIhDWGCKgSELR++cVd0cUAEGmy0AqFfj2KazYuZqsdJwUgHgXP7de+F1gtkjq5uQXlCD\r
+ /XGWL18S5frY8wD1NWYzNBH4FvkoqAjahZwqYCH6xesBXEIGQtAinNUUHUkVYYy8mHYh\r
+ RFvA==\r
+X-Gm-Message-State:\r
+ AD7BkJJC44hoZlSRAcjBd5GkYUKCNQ0xiyCt2cFyIhMquPWDpyzI4/Jx+KPf4FCtf7A9xQ==\r
+X-Received: by 10.194.119.201 with SMTP id kw9mr3743558wjb.173.1457612640707; \r
+ Thu, 10 Mar 2016 04:24:00 -0800 (PST)\r
+Received: from disaster-area.hh.sledj.net\r
+ ([2a01:348:1a2:1:ea39:35ff:fe2c:a227])\r
+ by smtp.gmail.com with ESMTPSA id j10sm3269145wjb.46.2016.03.10.04.23.59\r
+ (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
+ Thu, 10 Mar 2016 04:23:59 -0800 (PST)\r
+Received: from localhost (disaster-area.hh.sledj.net [local])\r
+ by disaster-area.hh.sledj.net (OpenSMTPD) with ESMTPA id a484147f;\r
+ Thu, 10 Mar 2016 12:23:58 +0000 (UTC)\r
+To: David Bremner <david@tethera.net>, Tomi Ollila <tomi.ollila@iki.fi>,\r
+ Matthew Lear <matt@bubblegen.co.uk>\r
+Cc: notmuch@notmuchmail.org\r
+Subject: Re: (emacs) Parsing problems replying to encrypted html\r
+In-Reply-To: <87ziu67cvh.fsf@zancas.localnet>\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> <87ziu67cvh.fsf@zancas.localnet>\r
+From: David Edmondson <dme@dme.org>\r
+Date: Thu, 10 Mar 2016 12:23:57 +0000\r
+Message-ID: <m2bn6mseqq.fsf@dme.org>\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: Thu, 10 Mar 2016 12:24:07 -0000\r
+\r
+On Thu, Mar 10 2016, David Bremner wrote:\r
+> Tomi Ollila <tomi.ollila@iki.fi> writes:\r
+>\r
+>> 2016-03-08 (Tue) 14:16:01: reply --format=sexp --format-version=1 --reply-to=sender thread:0000000000004a6f\r
+>> 2016-03-08 (Tue) 14:16:01: show --format=raw --part=2 id:56DDE706.6060702@bubblegen.co.uk\r
+>> 2016-03-08 (Tue) 14:16:01: show --format=sexp --include-html --part=3 id:56DDE706.6060702@bubblegen.co.uk\r
+>> 2016-03-08 (Tue) 14:16:01: show --format=raw --part=3 id:56DDE706.6060702@bubblegen.co.uk\r
+>>\r
+>> when replying from show:\r
+>>\r
+>> 2016-03-08 (Tue) 14:16:37: reply --format=sexp --format-version=1 --decrypt --reply-to=sender id:56DDE706.6060702@bubblegen.co.uk\r
+>> 2016-03-08 (Tue) 14:16:37: show --format=raw --part=2 id:56DDE706.6060702@bubblegen.co.uk\r
+>>\r
+>> there's no --decrypt when from search ... and interestingly there are other\r
+>> differences, too...\r
+>\r
+> That's useful log info, thanks Tomi. With dme's series\r
+> id:1457457179-4707-1-git-send-email-dme@dme.org I get the ciphertext\r
+> when replying from search-mode, which suggests there are at least two\r
+> bugs here.\r
+\r
+That's related to "notmuch reply --decrypt thread:something" I believe,\r
+which didn't seem to decrypt when I did a quick test (but I wasn't\r
+concentrating on that aspect of things).\r