From: Matthew Lear <matt@bubblegen.co.uk>
To: Brian Sniffen <bts@evenmere.org>
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Jani Nikula <jani@nikula.org>,
Vladimir Panteleev <thecybershadow@gmail.com>,
notmuch@notmuchmail.org
Subject: Re: web interface to notmuch
Date: Wed, 01 Nov 2017 13:01:59 +0000 [thread overview]
Message-ID: <CAJFxaw8nhUx0NeqtoR-=G5+W70KwxPr0Zu=pE0QcZJOxJka+xQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFxaw-izEFO-Epp0coxEpaRvYXsV-GuK7yA2L7=AnpTaHqANg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2358 bytes --]
Comparing with the Haskell based notmuch-web, while slightly slower to
render a browser page with the same search terms as nmweb, I can view the
email which causes nmweb to throw the encoding exception just fine in it. I
guess something in that implementation is able to handle encoding
differently.
Regards,
Matt
On Tue, 31 Oct 2017, 21:32 Matthew Lear, <matt@bubblegen.co.uk> wrote:
> On Tue, Oct 31, 2017 at 7:21 PM, Brian Sniffen <bts@evenmere.org> wrote:
>
>>
>> > I'm no Python expert, but from a quick google it would seem like the
>> cause
>> > of such an exception is related to not using utf-8.
>>
>> Neat. So to get there, this has to be a text/html part. It has to have
>> been decoded, either with the declared content type or with ascii. If a
>> \u201c (left double quote) showed up, it didn't get decoded as
>> ascii---and indeed, it looks like the content-type specifies latin-1.
>> But now when we try to encode back, using the same latin-1, it fails?
>> That's really neat.
>>
>> > Brian - do you think something needs modifying in nmweb.py to cater for
>> > this type of thing, or is this somehow related my own mailstore (not
>> sure
>> > why that would be as my messages haven't been modified).
>>
>> Lots of mail has busted encoding. I've done some defensive work against
>> that---look at decodeAnyway and shed a tear for purity---but clearly not
>> enough. Can you send me a message that causes the problem?
>>
>
> I'll need to fix up the text in the message because it's confidential.
> That should be easy enough to do.
> I'll send it to you once I've done that.
>
> One other thing - it looks like accessing attachments should work, but
> I've seen messages in my local set up here which have attachments shown,
> but I've not been able to retrieve them.
> Not sure what would cause that. Also some messages which are tagged as
> having attachments, don't have them shown by nmweb.
>
> FWIW this link (
> https://nmweb.evenmere.org/show/CACMMjMLecmXopb8AATjE3UuCnNLOO%2B5Nmev5X8K-UostDEUdrQ%40mail.gmail.com)
> has the tag attachment applied to the message, but there is no attachment
> shown. And another (
> https://nmweb.evenmere.org/show/87d31artti.fsf%40inf-8657.int-evry.fr).
>
> Maybe text/plain only emails are the ones which aren't problematic w.r.t.
> having their attachments shown?
> Cheers,
> -- Matt
>
>
>
[-- Attachment #2: Type: text/html, Size: 3590 bytes --]
next prev parent reply other threads:[~2017-11-01 13:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 14:43 web interface to notmuch Matthew Lear
2017-10-19 15:01 ` Brian Sniffen
2017-10-19 16:55 ` Daniel Kahn Gillmor
2017-10-19 20:00 ` Brian Sniffen
2017-10-19 20:13 ` Daniel Kahn Gillmor
2017-10-21 20:00 ` Jani Nikula
2017-10-21 22:21 ` Daniel Kahn Gillmor
2017-10-24 12:39 ` Vladimir Panteleev
[not found] ` <27e53def-32b4-45ab-1192-77cc0e837a93@gmail.com>
2017-10-24 20:03 ` Matthew Lear
2017-10-25 22:03 ` Brian Sniffen
2017-10-26 21:25 ` Daniel Kahn Gillmor
2017-10-27 4:04 ` Brian Sniffen
2017-10-27 4:24 ` Daniel Kahn Gillmor
2017-10-27 10:02 ` Matthew Lear
2017-10-27 6:05 ` Daniel Kahn Gillmor
2017-10-27 17:52 ` Brian Sniffen
2017-10-31 17:13 ` Matthew Lear
2017-10-31 18:47 ` Tomas Nordin
2017-10-31 19:21 ` Brian Sniffen
2017-10-31 21:32 ` Matthew Lear
2017-11-01 13:01 ` Matthew Lear [this message]
2017-11-01 14:38 ` Brian Sniffen
2017-11-02 17:32 ` Matthew Lear
2017-12-06 15:00 ` Brian Sniffen
2017-12-06 19:13 ` Daniel Kahn Gillmor
2017-12-07 1:00 ` David Bremner
2017-10-20 19:25 ` W. Trevor King
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='CAJFxaw8nhUx0NeqtoR-=G5+W70KwxPr0Zu=pE0QcZJOxJka+xQ@mail.gmail.com' \
--to=matt@bubblegen.co.uk \
--cc=bts@evenmere.org \
--cc=dkg@fifthhorseman.net \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.org \
--cc=thecybershadow@gmail.com \
/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).