unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: notmuch@notmuchmail.org
Subject: Re: notmuch-mode: Emails with PDF attachments incorrectly tagged as text/plain expose a few issues
Date: Tue, 07 Apr 2020 00:33:49 +0300	[thread overview]
Message-ID: <m2lfn8i9j6.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <87v9mccz4o.fsf@tethera.net>

On Mon, Apr 06 2020, David Bremner wrote:

> Leo Gaspard <leo@gaspard.io> writes:
>
>> David Bremner <david@tethera.net> writes:
>>
>>> Leo Gaspard <leo@gaspard.io> writes:
>>>
>>>> Hello,
>>>>
>>>> I have recently started conversing with someone whose email client
>>>> incorrectly tags PDF attachments as text/plain.
>>>>
>>>
>>> Hi Leo;
>>>
>>> As I mentioned on IRC, we most likely need a reproducer message before
>>> making any progress on this. Maybe you can ask your correspondent to
>>> send you a shareable message, then sanitize the addesses in the headers.
>>
>> So, I've just been able to re-create at least the “freeze on reply” isue
>> with the email attached. The image doesn't get corrupted when saving,
>> though, so I'm not sure it'll be enough to fix both issues, but
>> hopefully fixing this one would fix the other one too.
>>
>> If you try to notmuch-show on the attached email, then hit `r`, you
>> should notice the image being included verbatim in the text/plain
>> output, and when hitting C-c C-c it should start freezing emacs.
>>
>> Hope that helps!
>>   Leo
>
> Probably the rest of the list hasn't seen the message yet, but I did try
> it out. ...

Rest of the list hasn't seen the message (yet?) as the body is 440805 bytes
in size (and there is limit in the mailing list) and it is hanging in 
moderator queue. I am not too enthusiastic to bloat the mailing list
archive with just a large test message (but am not against is there more
people who do think that it is a good idea).

Tomi

> ... It doesn't actually hang emacs for me (C-g enough times gets me
> back). I agree that inserting binary data into the buffer is probably
> not a great idea.  I'm not sure offhand how notmuch should detect
> mislabeled parts. Perhaps it should just refuse to insert large parts as
> reply text.
>
> d

  parent reply	other threads:[~2020-04-06 21:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-05 23:12 notmuch-mode: Emails with PDF attachments incorrectly tagged as text/plain expose a few issues Leo Gaspard
2020-04-06 10:30 ` David Bremner
     [not found]   ` <87ftdgbnyr.fsf@llwynog.ekleog.org>
2020-04-06 17:17     ` David Bremner
2020-04-06 19:23       ` Leo Gaspard
2020-04-06 21:33       ` Tomi Ollila [this message]
2020-04-06 21:59         ` 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=m2lfn8i9j6.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --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).