From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Handling big mailing lists
Date: Wed, 29 Jul 2009 06:46:19 -0700 [thread overview]
Message-ID: <1248874122-sup-3830@masanjin.net> (raw)
In-Reply-To: <m3zlaovx3t.fsf@iny.iki.fi>
Hi,
Excellent set of questions. Handling large volumes of mail is one of my
main goals with Sup.
Reformatted excerpts from iny+dev's message of 2009-07-28:
> I tried to test Sup, but I wasn't able to get any emails because Sup
> failed to login to my IMAP server. This happened because the server
> requires client certificates and it looks like Sup doesn't support
> those.
As far as IMAP goes, Sup supports whatever authentication the Ruby IMAP
libraries supports, which is probably not much.
Any serious use of Sup with IMAP is best done via an intermediate like
offlineimap, which syncs an IMAP folder to a local Maildir folder. The
Ruby IMAP libraries, and possibly IMAP itself, is a little too slow for
how Sup likes to work.
> How would my daily reading routine work with Sup? I want to read
> things in priority order:
>
> 1. Personal email
> 2. Emails related to my programming hobby
> 3. Emails related to some associations like user groups
> 4. Mailing lists, also in priority order
Sup gives you two tools: search and labels. Sup will present a list of
threads that match any search query. So, each of those steps is
possible, to the extent that you can compose a search query that
reflects it.
You can automatically add labels via arbitrary code, so you have a fair
amount of flexibility here.
> The order is such that if I need to stop reading, I have read the most
> important ones already. The order is not static, I want to be able to
> change it. I have understood that labels are way to get this kind of
> grouping. Can I get a view where the labels are sorted like this?
Sup currently only orders chronologically. It would not be difficult to
add a second level of user-defined sorting *on top* of the chronological
one, but it would be difficult, if not impossible, to order all email in
the index by an arbitrary function.
(To be pedantic, if you can come up with a single number for each email,
which never changes, and which is known at add time, you can order by
that, with some work. But it doesn't sound like that's what you want.)
> And can I continue reading the next label in that order after I have
> finished the one before?
Certainly, but not automatically. You can view one label, and then pick
another label to view, etc.
I suppose if the above second-round of ordering were implemented, you
could view both labels at once and make an ordering function that placed
one above the other.
> Then about the expiration. The linux-kernel mailing list gets so much
> email that some kind of expiration is a must.
You don't want to just buy a bigger hard drive?
> Can Sup do such automatic deleting of old emails? Can Sup handle some
> other process doing such automatic deletion? (I would actually prefer
> some other process do it.)
That's best left to another process. You'll then have to tell Sup which
messages were deleted so that it can remove them from the index. Let me
know when you're at this point and I can help you---it will require a
brief Ruby script.
> I would actually recommend reading linux-kernel to test Sup. :)
I read ruby-talk, which is probably not too far off.
One last comment: large threads are irritatingly slow to create in
thread-view-mode with the Ferret index, but there's a new Xapian index
which is fast for this. It's still slightly experimental.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-07-29 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 6:09 Ilpo Nyyssönen
2009-07-29 12:54 ` Marc Weber
2009-07-29 13:46 ` William Morgan [this message]
2009-07-29 17:24 ` Ilpo Nyyssönen
2009-08-03 17:31 ` William Morgan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1248874122-sup-3830@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox