Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id A4F4A2E2D80 for ; Wed, 12 Mar 2008 06:11:21 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 20025-06 for ; Wed, 12 Mar 2008 06:11:18 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.232]) by postgresql.org (Postfix) with ESMTP id C6B362E162B for ; Wed, 12 Mar 2008 06:11:17 -0300 (ADT) Received: by wr-out-0506.google.com with SMTP id c49so2063936wra.19 for ; Wed, 12 Mar 2008 02:11:16 -0700 (PDT) Received: by 10.150.138.8 with SMTP id l8mr4361806ybd.141.1205313076764; Wed, 12 Mar 2008 02:11:16 -0700 (PDT) Received: by 10.150.96.5 with HTTP; Wed, 12 Mar 2008 02:11:16 -0700 (PDT) Message-ID: <937d27e10803120211s683daf1v67513ac44bed4cca@mail.gmail.com> Date: Wed, 12 Mar 2008 09:11:16 +0000 From: "Dave Page" To: "Tom Lane" Subject: Re: Email not searchable in our archives Cc: "Alvaro Herrera" , "Joshua D. Drake" , "Bruce Momjian" , "PostgreSQL www" In-Reply-To: <9934.1205284343@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200803112135.m2BLZ6625071@momjian.us> <20080311220224.GC6737@alvh.no-ip.org> <20080311152012.3bd779b9@jd-laptop> <20080312010346.GE6737@alvh.no-ip.org> <9934.1205284343@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/243 X-Sequence-Number: 14362 On Wed, Mar 12, 2008 at 1:12 AM, Tom Lane wrote: > Alvaro Herrera writes: > > I don't want to lose Mhonarc, at least not for the moment. It is > > powerful and customizable and has served us reasonably well for a very > > long time. (Longer than most of us, actually.) > > Agreed. One of the problems with moving off it is that if we change to > something else that breaks mbox files at different points, we will > invalidate archive URLs. We went there once already by accident and it > was not fun. The replacement archives system I've been working on takes it's data from the existing monthly mboxes, and although it uses it's own URL scheme, it does understand and accept the old URLs. That (and fixing the thread-breaks-over-a-month issue) we pretty much my top requirements. -- Dave Page EnterpriseDB UK Ltd: http://www.enterprisedb.com PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk