From: iny+dev@iki.fi (Ilpo Nyyssönen)
Subject: [sup-talk] Handling big mailing lists
Date: Wed, 29 Jul 2009 09:09:42 +0300 [thread overview]
Message-ID: <m3zlaovx3t.fsf@iny.iki.fi> (raw)
I'm searching alternatives for my Gnus email + news setup. I don't
expect Sup to be able to do everything Gnus can yet, but maybe in
future? :) Note that I have never used Gmail.
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.
The bigger question is about handling big amount of mailing list mail.
I'm reading many small mailing lists and some big ones. Biggest is
linux-kernel. I can split this to two: daily reading routine and
expiration.
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
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? And can I
continue reading the next label in that order after I have finished
the one before?
Then about the expiration. The linux-kernel mailing list gets so much
email that some kind of expiration is a must. 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.)
I'm mostly reading just only few authors from linux-kernel and skipping
rest, but I do like to see the rest in the thread view as sometimes some
subject is interesting and sometimes some thread gets big and is
interesting because of that. How would this work?
I would actually recommend reading linux-kernel to test Sup. :)
--
Ilpo Nyyss?nen # biny # /* :-) */
next reply other threads:[~2009-07-29 6:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 6:09 Ilpo Nyyssönen [this message]
2009-07-29 12:54 ` Marc Weber
2009-07-29 13:46 ` William Morgan
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=m3zlaovx3t.fsf@iny.iki.fi \
--to=iny+dev@iki.fi \
/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