From: Ben Walton <bwalton@artsci.utoronto.ca>
To: Matthias Vallentin <vallentin@icsi.berkeley.edu>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] current state of synching upstream?
Date: Sat, 18 Dec 2010 14:21:40 -0500 [thread overview]
Message-ID: <1292699674-sup-8221@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <20101218190427.GU60419@icsi.berkeley.edu>
Excerpts from Matthias Vallentin's message of Sat Dec 18 14:04:27 -0500 2010:
> The downside appears to be that each rotation adds, in the above
> example, 10 new source entries to sources.yaml and requires
> switching of polling in the non-current sources.
Here's my current approach that I've been happy with since I
implemented it back in the summer:
1. Procmail files all mail (regardless of originating source) into
Maildirs like .incoming.%Y.%m. This gives me a new maildir each month
that holds all incoming mail for that month. The basics of the
.procmailrc to do this are:
--snip--
MAILDIR=$HOME/Maildir/
DATEDIR=`date +%Y.%m`
:0
$MAILDIR/.incoming.$DATEDIR/
--snip--
2. I have the following hook setup as after-poll:
--snip--
s = "maildir:/path/to/Maildir/.incoming.#{Date.today.strftime("%Y.%m")}"
unless Redwood::SourceManager.source_for(s)
Redwood::Logger.force_message "Adding new source: #{s}"
Redwood::SourceManager.add_source Recoverable.new(Redwood::Maildir.new(s))
end
--snip--
3. I have almost all of my labelling done via the before-add-message
hook. This gets me the per-mailing-list tags that I would have
applied based on source originally. I almost never apply tags
manually any more.
The only downside to this is that my sources.yaml file needs manual
twiddling at restart to add the sources that were added during
runtime. I've yet to be annoyed enough by this to figure out how to
make these dynamic additions sticky across restarts.
HTH.
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-12-18 19:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 9:40 Ryan Barrett
2010-04-11 17:52 ` Ryan Barrett
2010-04-12 0:57 ` Rich Lane
2010-04-12 5:02 ` Andrew Pimlott
2010-04-12 12:11 ` Daemian Mack
2010-04-12 9:53 ` Tero Tilus
2010-04-14 13:00 ` William Morgan
2010-04-14 14:16 ` Ben Walton
2010-04-14 15:57 ` William Morgan
2010-04-14 16:08 ` Ben Walton
2010-12-15 8:19 ` Matthias Vallentin
2010-12-15 17:06 ` James Taylor
2010-12-18 5:12 ` Matthias Vallentin
2010-12-18 5:25 ` James Taylor
2010-12-18 19:04 ` Matthias Vallentin
2010-12-18 19:21 ` Ben Walton [this message]
2010-12-18 20:02 ` Tero Tilus
2010-12-18 20:12 ` Ben Walton
2010-12-21 6:44 ` Matthias Vallentin
2010-12-21 6:48 ` Matthias Vallentin
2010-12-21 11:01 ` Tero Tilus
2010-12-21 14:11 ` Ben Walton
2010-12-22 14:42 ` Matthias Vallentin
2010-12-22 16:27 ` Tero Tilus
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=1292699674-sup-8221@pinkfloyd.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--cc=sup-talk@rubyforge.org \
--cc=vallentin@icsi.berkeley.edu \
/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