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 AABCF6DE01F5 for ; Tue, 8 Mar 2016 06:06:48 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.66 X-Spam-Level: X-Spam-Status: No, score=-0.66 tagged_above=-999 required=5 tests=[AWL=0.040, RCVD_IN_DNSWL_LOW=-0.7] 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 ipzM4_zLZXEi for ; Tue, 8 Mar 2016 06:06:47 -0800 (PST) Received: from avasout04.plus.net (avasout04.plus.net [212.159.14.19]) by arlo.cworth.org (Postfix) with ESMTPS id B753A6DE020B for ; Tue, 8 Mar 2016 06:06:44 -0800 (PST) Received: from localhost ([84.93.237.98]) by avasout04 with smtp id TS6h1s006283uBY01S6ilC; Tue, 08 Mar 2016 14:06:42 +0000 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.1 cv=K//fZHiI c=1 sm=1 tr=0 a=BJaFPv9AyABFDM2hXLRoEA==:117 a=BJaFPv9AyABFDM2hXLRoEA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=8nJEP1OIZ-IA:10 a=7OsogOcEt9IA:10 a=80hmnl3cAAAA:8 a=nTBm7qOPAKf81V_2nAYA:9 a=9h0y6MHcAV6JqX-w:21 a=O4tOLaTqGRudZjUL:21 a=wPNLvfGTeEIA:10 Received: from localhost ([127.0.0.1] helo=webmail.plus.net) by localhost with esmtp (Exim 4.76) (envelope-from ) id 1adIHZ-00087u-5V; Tue, 08 Mar 2016 14:06:41 +0000 Received: from 216.31.211.11 (proxying for unknown) (SquirrelMail authenticated user bubblegen+matt) by webmail.plus.net with HTTP; Tue, 8 Mar 2016 14:06:41 -0000 Message-ID: In-Reply-To: References: <56DD48B3.90604@bubblegen.co.uk> <87mvqatr6y.fsf@zancas.localnet> <87h9gigfyz.fsf@bubblegen.co.uk> <87pov58b9y.fsf@zancas.localnet> Date: Tue, 8 Mar 2016 14:06:41 -0000 Subject: Re: (emacs) Parsing problems replying to encrypted html From: "Matthew Lear" To: "Tomi Ollila" Cc: "David Bremner" , "Matthew Lear" , "David Edmondson" , 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: Tue, 08 Mar 2016 14:06:48 -0000 > On Tue, Mar 08 2016, Tomi Ollila wrote: > >> [ text/plain ] >> On Tue, Mar 08 2016, David Bremner wrote: >> >>> [ text/plain ] >>> Matthew Lear writes: >>> >>> >>> Thanks for the test case. I can duplicate a (the?) bug as >>> follows. Replying to that message from notmuch-show mode works, but >>> replying from notmuch-search mode yields >>> >>>> !!! Bodypart insert error: Wrong type argument: number-or-marker-p, >>>> nil !!! >>>> [ application/pgp-encrypted ] >>>> Version: 1 >>>> [ encrypted.asc: application/octet-stream (as text/plain) ] >>>> !!! Bodypart insert error: Internal error: No :content from ("show" >>>> "--format=sexp" "--include-html" "--part=3" >>>> "id:56DDE706.6060702@bubblegen.co.uk") !!! >>> >>> Followed by the ciphertext. >>>> -----BEGIN PGP MESSAGE----- >>> >>> If anyone wants to play with this, you just need to import the notmuch >>> test key into your keyring, something like >>> >>> gpg --import path/to/notmuch-source/test/gnupg-secret-key.asc >>> >>> What's odd is that the notmuch command in the error message works on >>> the >>> command line. >> >> I got these to my log: >> >> when replying from search: >> >> 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 > > The above line returns (same as in latest !!! bodypart insert error !!!) > > (:id 3 :content-type "application/octet-stream" :filename "encrypted.asc" > :content-length 1875) > > -- there is no content to be included from that line :/ (and wat is this > "encrypted.asc" anyway ?) encrypted.asc is what Enigmail uses when sending using PGP/MIME. I think it wraps up the message body in this file (armor encrypted) and marks it with disposition inline. Enigmail also sends PGP/MIME version identification information in another MIME part (application/pgp-encrypted) - so you have two MIME parts per PGP/MIME encrypted message. You can view all headers in the test message if you're in notmuch-show by using V. You'll see something like: Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; boundary="xxx" This is an OpenPGP/MIME encrypted message (RFC 4880 and 3156) --xxx Content-Type: application/pgp-encrypted Content-Description: PGP/MIME version identification Version: 1 --xxx Content-Type: application/octet-stream; name="encrypted.asc" Content-Description: OpenPGP encrypted message Content-Disposition: inline; filename="encrypted.asc" -----BEGIN PGP MESSAGE----- Version: GnuPG v2 ... -----END PGP MESSAGE----- --xxx--