From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Question regarding Maildir (and possible patch?)
Date: Mon, 08 Oct 2007 14:26:37 -0700 [thread overview]
Message-ID: <1191877732-sup-6395@south> (raw)
In-Reply-To: <001601c807f3$c6bafe10$650aa8c0@ocean>
Excerpts from steve.shreeve's message of Sat Oct 06 01:34:55 -0700 2007:
> Since I prefer not to manually add all 1,500 mailboxes as "sources"
> for sup, I modified maildir.rb as follows to allow sup to dive into
> mailboxes.
This is a very nice solution, but after some thought I'm not going to
apply it. Maildir folders should be handled the same way that mbox
folders are: each as its own source. If you have lots of them, use
sup-add from the command line in conjunction with shell globbing or the
find command.
The reason is that per-folder auto-applied labels are still important
(at least until I get filtering working), and you lose that capability
with recursion. One could make recursion a configurable property of a
Maildir source, though it strikes me as possibly overengineering.
Depends how many people would actually use it.
When this issue has come up before, my proposed solution has been to
modify sup-config to do the recursion for you at setup time. This is not
a high priority change since my target audience is the Unix-savvy.
In your case, 1500 folders is a lot, but Sup should be able to handle
it. I recommend adding them as unpolled sources---unless, of course,
they do receive new mail---so as to avoid slowing down new message
polling. (In Sup terminology these are (regrettably) called "unpolled"
sources.)
Please don't let this discourage you from sending more patches, of
course! :)
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-10-08 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 8:34 Steve Shreeve
2007-10-08 21:26 ` William Morgan [this message]
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=1191877732-sup-6395@south \
--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