Re: [sup-talk] current state of synching upstream?

From: Matthias Vallentin <vallentin@icsi.berkeley.edu>
To: Ben Walton <bwalton@artsci.utoronto.ca>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] current state of synching upstream?
Date: Wed, 15 Dec 2010 00:19:55 -0800	[thread overview]
Message-ID: <20101215081955.GF568@icsi.berkeley.edu> (raw)
In-Reply-To: <1271261164-sup-4109@pinkfloyd.chass.utoronto.ca>

On Wed, Apr 14, 2010 at 12:08:14PM -0400, Ben Walton wrote:
> Big (notice the size of the new/ directory), but not huge.  Poll times
> increase linearly though, which one drawback to the current approach
> of not moving mail into cur/ when it's detected.

Does the current version of sup still keep mail in new? As a fairly new
sup user, I am trying to understand the limitations of maildir support
and this one seems to be one.

My traditional mindest is still similar to logrotate, i.e., regularly
copying maildirs into an archive. If this is still an issue, what about
an where mail directories with more than X messages are being
automatically copied to an archive? This would bound the linear poll
times at a configurable threshold. I don't know how this would look like
(adding a new source per rotated maildir does not seem a nice solution)
and how it would interplay with Xapian. For example, I worry that
maildir rotation could involve major index rebuilding.

   Matthias
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk