From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id D8A166DE02CA for ; Fri, 1 Apr 2016 04:54:52 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.676 X-Spam-Level: X-Spam-Status: No, score=-0.676 tagged_above=-999 required=5 tests=[AWL=0.044, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F0idG8V0mxhN for ; Fri, 1 Apr 2016 04:54:44 -0700 (PDT) Received: from avasout07.plus.net (avasout07.plus.net [84.93.230.235]) by arlo.cworth.org (Postfix) with ESMTPS id 491BE6DE014A for ; Fri, 1 Apr 2016 04:54:43 -0700 (PDT) Received: from webmail04.plus.net ([84.93.228.66]) by avasout07 with smtp id czue1s0061SbfYc01zueX2; Fri, 01 Apr 2016 12:54:41 +0100 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.1 cv=QqujpgGd c=1 sm=1 tr=0 a=C5+YawzV8SR07mwocaP9vA==:117 a=Pqgwzd+QtBWunNm/3vzkeA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=8nJEP1OIZ-IA:10 a=kziv93cY1bsA:10 a=80hmnl3cAAAA:8 a=H4IEW4q-AAAA:8 a=s0WE9tTHO0dr_0nI06gA:9 a=UtrO4ZA9eFxkQR56:21 a=pt_hz_2jTyl5iCce:21 a=wPNLvfGTeEIA:10 Received: from localhost ([127.0.0.1] helo=webmail.plus.net) by webmail04.plus.net with esmtp (Exim 4.76) (envelope-from ) id 1alxew-0000Vx-5l; Fri, 01 Apr 2016 12:54:38 +0100 Received: from 216.31.211.11 (proxying for unknown) (SquirrelMail authenticated user bubblegen+matt) by webmail.plus.net with HTTP; Fri, 1 Apr 2016 12:54:38 +0100 Message-ID: <575b60a1d39a1ecc7d06e5c0d625be61.squirrel@webmail.plus.net> In-Reply-To: <87oa9timv7.fsf@zancas.localnet> References: <56DD48B3.90604@bubblegen.co.uk> <87mvqatr6y.fsf@zancas.localnet> <87h9gigfyz.fsf@bubblegen.co.uk> <87pov58b9y.fsf@zancas.localnet> <87wpp76ctq.fsf@zancas.localnet> <87h9fm315q.fsf@bubblegen.co.uk> <87oa9timv7.fsf@zancas.localnet> Date: Fri, 1 Apr 2016 12:54:38 +0100 Subject: Re: (emacs) Parsing problems replying to encrypted html From: "Matthew Lear" To: "David Bremner" Cc: notmuch@notmuchmail.org Reply-To: matt@bubblegen.co.uk User-Agent: SquirrelMail MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 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: Fri, 01 Apr 2016 11:54:53 -0000 > Matthew Lear writes: > >> On Sat, Mar 12 2016 at 2:37:44 pm GMT, David Edmondson >> wrote: >>> On Sat, Mar 12 2016, David Bremner wrote: >>>> Tomi Ollila writes: >>>> >>>>> 2016-03-08 (Tue) 14:16:01: reply --format=sexp --format-version=1 >>>>> --reply-to=sender thread:0000000000004a6f >>>>> 2016-03-08 (Tue) 14:16:01: show --format=raw --part=2 >>>>> id:56DDE706.6060702@bubblegen.co.uk >>>>> 2016-03-08 (Tue) 14:16:01: show --format=sexp --include-html --part=3 >>>>> id:56DDE706.6060702@bubblegen.co.uk >>>>> 2016-03-08 (Tue) 14:16:01: show --format=raw --part=3 >>>>> id:56DDE706.6060702@bubblegen.co.uk >>>>> >>>> >>>> I think the problem is in the following let form, which uses >>>> notmuch-show-process-crypto. That isn't set in search mode. I'm >>>> unclear >>>> on what the right solution is here; we could check >>>> notmuch-crypto-process-mime, but I'm not sure how this would interact >>>> with the handling of prefix arguments (for temporary toggling). >>> >>> Is "reply" from search mode a common pattern of use? Currently it seems >>> generally un-useful (the thread has to contain just a single message - >>> not just a single matching message). >>> >>>> (defun notmuch-mua-reply (query-string &optional sender reply-all) >>>> (let ((args '("reply" "--format=sexp" "--format-version=1")) >>>> (process-crypto notmuch-show-process-crypto) >>>> reply >>>> original) >> >> Hi. I just wondered if anyone had managed to make any progress on this? > > Hi Matthew; > > I'm not sure if you noticed, but there are patches in master now (and > will be in a release pretty soon) that handle the part of the problem > related to encrypted html, but nothing so far for the problem(s) of > replying from search view. Thanks David. I've just pulled and rebuilt and can see a difference. When replying from show view, I see no quoted text from the original message, but when I reply from search view I see the inline PGP ciphertext quoted in the reply. I can understand the latter but not the former - this still looks like a bug, especially since if I reply from show view to a plain text encrypted message, I do see the original message quoted in the reply. -- Matt