From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.218.138 with SMTP id hq10cs9624icb; Wed, 15 Dec 2010 00:49:21 -0800 (PST) Received: by 10.150.58.5 with SMTP id g5mr9669435yba.216.1292402960674; Wed, 15 Dec 2010 00:49:20 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id l25si1057019vby.80.2010.12.15.00.49.20; Wed, 15 Dec 2010 00:49:20 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 408D31858356; Wed, 15 Dec 2010 03:49:20 -0500 (EST) Received: from gateway0.EECS.Berkeley.EDU (gateway0.EECS.Berkeley.EDU [169.229.60.87]) by rubyforge.org (Postfix) with ESMTP id 233CE1858356 for ; Wed, 15 Dec 2010 03:20:20 -0500 (EST) Received: from icsi.berkeley.edu (wangari.CS.Berkeley.EDU [169.229.3.78]) (authenticated bits=0) by gateway0.EECS.Berkeley.EDU (8.14.4/8.13.5) with ESMTP id oBF8Jt6F005183 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 Dec 2010 00:19:57 -0800 (PST) Date: Wed, 15 Dec 2010 00:19:55 -0800 From: Matthias Vallentin To: Ben Walton Message-ID: <20101215081955.GF568@icsi.berkeley.edu> Mail-Followup-To: Ben Walton , sup-talk References: <1271023429-sup-9851@zyrg.net> <1271249704-sup-1088@masanjin.net> <1271254358-sup-3024@pinkfloyd.chass.utoronto.ca> <1271260552-sup-9153@masanjin.net> <1271261164-sup-4109@pinkfloyd.chass.utoronto.ca> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1271261164-sup-4109@pinkfloyd.chass.utoronto.ca> X-PGP-Fingerprint: 8A3B 1323 B469 CCBA 54D3 3BCC D5E7 8DF5 9C8D 4B41 User-Agent: Mutt/1.5.20 (2009-06-14) Cc: sup-talk Subject: Re: [sup-talk] current state of synching upstream? X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org 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