From: "Matthew Lear" <matt@bubblegen.co.uk>
To: "David Edmondson" <dme@dme.org>
Cc: matt@bubblegen.co.uk, notmuch@notmuchmail.org
Subject: Re: (emacs) Parsing problems replying to encrypted html
Date: Tue, 1 Mar 2016 13:59:09 -0000 [thread overview]
Message-ID: <c4ff9f2c141441be10b1cb4b1e0300a7.squirrel@webmail.plus.net> (raw)
In-Reply-To: <m2a8miwc6x.fsf@dme.org>
> There is probably a bug here.
>
> On Tue, Mar 01 2016, Matthew Lear wrote:
>> Notmuch shows this as:
>>
>> [ multipart/encrypted ]
>> [ Decryption successful ]
>> [ Good signature by: xxxx ]
>> [ application/pgp-encrypted ]
>> Version: 1
>> [ multipart/mixed ]
>> [ multipart/alternative ]
>> [ text/plain (hidden) ]
>> [ multipart/related ]
>> [ text/html (hidden) ]
>> [ image.jpg: image/jpeg (hidden) ]
>
> You're saying here that you don't get shown the text/html part?
Apologies. No, I do get shown the text/html part. I just collapsed all the
parts here for illustration purposes.
>> (setq notmuch-multipart/alternative-discouraged '("text/plain"
>> "multipart/related"))
>
> I'm curious to understand why you discourage multipart/related. That's
> almost always used to wrap a text/html part with an image/jpg that the
> text/html part refers to by cid:.
Fair point. I think I had this discouraged as a hangover from having to
deal with malformatted PGP encrypted emails. I don't receive emails from
people which have been encrypted with that sw any more so I should
probably remove it. Even with multipart/related discouraged though, I
don't have any problem with embedded images / cid etc. All displayed ok.
> Are things different if you discourage only text/plain?
Nope. No change.
next prev parent reply other threads:[~2016-03-01 13:59 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 [this message]
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
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=c4ff9f2c141441be10b1cb4b1e0300a7.squirrel@webmail.plus.net \
--to=matt@bubblegen.co.uk \
--cc=dme@dme.org \
--cc=notmuch@notmuchmail.org \
/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).