Re: web interface to notmuch

Brian Sniffen writes: >> Assuming that you had a sanitize_this_html_part() function available to >> you, do you think it would be possible to make this safe? Have you >> considered proposing it for inclusion in contrib upstream? > > Okay,

Re: web interface to notmuch

Hi Brian-- On Wed 2017-12-06 10:00:19 -0500, Brian Sniffen wrote: > Okay, https://github.com/briansniffen/notmuch/tree/nmweb is now rebased > onto the notmuchmail.org head as of this morning. All of the changes > are under contrib/notmuch-web. thanks for doing this! traditionally, we've

Re: web interface to notmuch

> Assuming that you had a sanitize_this_html_part() function available to > you, do you think it would be possible to make this safe? Have you > considered proposing it for inclusion in contrib upstream? Okay, https://github.com/briansniffen/notmuch/tree/nmweb is now rebased onto the

Re: web interface to notmuch

On Wed, 1 Nov 2017, 14:38 Brian Sniffen, wrote: > On Oct 31, 2017, at 5:32 PM, Matthew Lear wrote > > I’ll push some fixes to encoding to github later today. > I've just tested with e3ba123 and there is a significant improvement. Also, attachments can

Re: web interface to notmuch

> On Oct 31, 2017, at 5:32 PM, Matthew Lear wrote: > > > 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

Re: web interface to notmuch

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

Re: web interface to notmuch

On Tue, Oct 31, 2017 at 7:21 PM, Brian Sniffen 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

Re: web interface to notmuch

> just remove it), but along the way of searching and viewing mail, I've > encountered quite a few occurrences of failing to UnicodeEncode. An example > backtrace looks like this: > > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/web/application.py", line 239, in >

Re: web interface to notmuch

On Fri, 27 Oct 2017, 18:52 Brian Sniffen, wrote: > Daniel Kahn Gillmor writes: > > > On Fri 2017-10-27 00:04:21 -0400, Brian Sniffen wrote: > >> With bleach integrated (all of five lines), I think this is safe enough > >> to let random notmuch users

Re: web interface to notmuch

Daniel Kahn Gillmor writes: > On Fri 2017-10-27 00:04:21 -0400, Brian Sniffen wrote: >> With bleach integrated (all of five lines), I think this is safe enough >> to let random notmuch users run it. > > hm, bleach might be a little too aggressive. > > jrollins just

Re: web interface to notmuch

On Fri 2017-10-27 00:04:21 -0400, Brian Sniffen wrote: > With bleach integrated (all of five lines), I think this is safe enough > to let random notmuch users run it. hm, bleach might be a little too aggressive. jrollins just pointed toward:

Re: web interface to notmuch

I've had a play with this this morning. It's great! The speed and page loading efficiency is fantastic. Would be really nice if we could go next/previous in the thread (yes I know I'm complaining about one extra mouse click). Also, if I select a date via the drop down I need to delete the

Re: web interface to notmuch

Daniel Kahn Gillmor writes: > On Wed 2017-10-25 18:03:01 -0400, Brian Sniffen wrote: >> That's inspiring! Now there's a demo of nmweb at >> >> https://nmweb.evenmere.org/ > > this is very nice, Brian. Thanks! The part I'm happiest about is the speed: this is as fast as

Re: web interface to notmuch

On Wed 2017-10-25 18:03:01 -0400, Brian Sniffen wrote: > That's inspiring! Now there's a demo of nmweb at > > https://nmweb.evenmere.org/ this is very nice, Brian. Your URL highlighter seems a bit trigger-happy though: https://nmweb.evenmere.org/show/8760s7zr47.fsf%40zancas.localnet I

Re: web interface to notmuch

That's inspiring! Now there's a demo of nmweb at https://nmweb.evenmere.org/ It's possible to get it to dump the whole mbox by clicking through the obvious links; please consider exploring at https://nmweb.evenmere.org/search/monkey instead. There are not many monkeys in the inbox. -Brian

Re: web interface to notmuch

Thanks for doing that, and thanks to all for the feedback and input so far. For the interface I want to set up, I'd like the ability to enter notmuch search syntax in an input box, and also show tags applied to messages. The interface presented by the current version of notmuch-web ticks a lot of

Re: web interface to notmuch

Hi, Sorry to barge in, I noticed this thread and thought I'd try to have a go at setting up a test DFeed instance. Here it is: http://dfeed-notmuch.k3.1azy.net/ There is some more info on the help page: http://dfeed-notmuch.k3.1azy.net/help Posting is supported, but it is currently

Re: web interface to notmuch

On Sat 2017-10-21 23:00:00 +0300, Jani Nikula wrote: > For the list archive, we could restrict to displaying text/plain only. and text/x-diff, surely :) But yeah, good point. Brian, what do you think about such a constraint? would that make your implementation safe enough to put on the public

Re: web interface to notmuch

On Thu, 19 Oct 2017, Daniel Kahn Gillmor wrote: > On Thu 2017-10-19 11:01:53 -0400, Brian Sniffen wrote: >> I put together something like this, visible at >> https://github.com/briansniffen/notmuch/tree/nmweb/contrib/notmuch-web >> >> It's not much of a service. I am

Re: web interface to notmuch

I haven't looked at the backing code in a while, but I really like the public-inbox [1] approach to archival. Since Gmane died, Git (and a few other projects [2]) have also been using the author's hosted version. I haven't looked at the backing code in a while, but it's live Perl, not a static

Re: web interface to notmuch

On Thu 2017-10-19 16:00:33 -0400, Brian Sniffen wrote: > I don’t think they can be sanitized. Web tech moves so fast. well, there are at least a handful of python modules that claim to do some sort of sanitization. in debian alone, we have at least: python3-django-html-sanitizer

Re: web interface to notmuch

> On Oct 19, 2017, at 12:55 PM, Daniel Kahn Gillmor > wrote: > >> On Thu 2017-10-19 11:01:53 -0400, Brian Sniffen wrote: >> I put together something like this, visible at >> https://github.com/briansniffen/notmuch/tree/nmweb/contrib/notmuch-web >> >> It's not much of a

Re: web interface to notmuch

On Thu 2017-10-19 11:01:53 -0400, Brian Sniffen wrote: > I put together something like this, visible at > https://github.com/briansniffen/notmuch/tree/nmweb/contrib/notmuch-web > > It's not much of a service. I am pretty sure it is exploitable---that > content in text/html parts of messages can

Re: web interface to notmuch

I put together something like this, visible at https://github.com/briansniffen/notmuch/tree/nmweb/contrib/notmuch-web It's not much of a service. I am pretty sure it is exploitable---that content in text/html parts of messages can do Bad Things to your session. I haven't thought nearly hard

web interface to notmuch

Hello all. A little side project at work involves me trying to put together part of a knowledge share system where users can query and search email stored and indexed centrally (by offlineimap & notmuch). My intention is to provide a means to support multiple concurrent read-only accesses to the

[notmuch] noneatall - a silly web interface for notmuch

DraX on IRC asked, so here's a git repository: git://github.com/dme/noneatall.git dme. -- David Edmondson, http://dme.org

[notmuch] noneatall - a silly web interface for notmuch

Whilst thinking about web interfaces for notmuch I decided that it would be quicker to implement one and play rather than trying to consider all possibilities. The result is noneatall[1]. It's _very_ simple and pretty nasty. Please look at the source before you use it - there are no doubt a