From: "Matthew Lear" <matt@bubblegen.co.uk>
To: "Tomi Ollila" <tomi.ollila@iki.fi>
Cc: "David Bremner" <david@tethera.net>,
"Matthew Lear" <matt@bubblegen.co.uk>,
"David Edmondson" <dme@dme.org>,
notmuch@notmuchmail.org
Subject: Re: (emacs) Parsing problems replying to encrypted html
Date: Tue, 8 Mar 2016 14:06:41 -0000 [thread overview]
Message-ID: <ac9b21e31f5581025ff92fd70a8cef79.squirrel@webmail.plus.net> (raw)
In-Reply-To: <m21t7lkuts.fsf@guru.guru-group.fi>
> On Tue, Mar 08 2016, Tomi Ollila wrote:
>
>> [ text/plain ]
>> On Tue, Mar 08 2016, David Bremner wrote:
>>
>>> [ text/plain ]
>>> Matthew Lear <matt@bubblegen.co.uk> 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--
next prev parent reply other threads:[~2016-03-08 14:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 13:09 (emacs) Parsing problems replying to encrypted html Matthew Lear
2016-03-01 13:38 ` David Edmondson
2016-03-01 13:59 ` Matthew Lear
2016-03-07 9:24 ` Matthew Lear
2016-03-07 12:20 ` David Bremner
2016-03-07 21:01 ` Matthew Lear
2016-03-08 11:22 ` David Bremner
2016-03-08 11:44 ` Matthew Lear
2016-03-08 12:08 ` David Bremner
2016-03-08 12:28 ` Matthew Lear
2016-03-08 12:26 ` Tomi Ollila
2016-03-08 12:39 ` Tomi Ollila
2016-03-08 14:06 ` Matthew Lear [this message]
2016-03-10 12:09 ` David Bremner
2016-03-10 12:23 ` David Edmondson
2016-03-12 13:33 ` David Bremner
2016-03-12 14:37 ` David Edmondson
2016-03-13 16:09 ` Jani Nikula
2016-03-14 8:32 ` David Edmondson
2016-03-31 19:20 ` Matthew Lear
2016-04-01 11:34 ` David Bremner
2016-04-01 11:54 ` Matthew Lear
2016-04-01 13:28 ` David Bremner
2016-04-01 13:58 ` Matthew Lear
2016-04-01 18:29 ` Matthew Lear
2016-04-01 23:24 ` David Bremner
2016-04-03 18:42 ` David Edmondson
2016-07-22 16:47 ` Matthew Lear
2016-07-23 13:40 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac9b21e31f5581025ff92fd70a8cef79.squirrel@webmail.plus.net \
--to=matt@bubblegen.co.uk \
--cc=david@tethera.net \
--cc=dme@dme.org \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).