Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 946352E02E6 for ; Wed, 12 Mar 2008 05:18:28 -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 09887-01 for ; Wed, 12 Mar 2008 05:18:25 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 2FAFC2E0238 for ; Wed, 12 Mar 2008 05:18:25 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id 9A639DCC8D4; Wed, 12 Mar 2008 09:18:23 +0100 (CET) From: "Magnus Hagander" To: "Joshua D. Drake" CC: "Alvaro Herrera" , "Bruce Momjian" , "PostgreSQL www" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Message-ID: <200803120917460000@2319429249> Subject: Re: Email not searchable in our archives Date: Wed, 12 Mar 2008 09:17:46 +0100 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/239 X-Sequence-Number: 14358 > > Perhaps I should just try without the subdir and see if it works. > > I am wondering if we should bail out of Mhonarc all together. Do we > actually need it? We have the actual mbox files right? Couldn't we > build our own parser for whatever? Let's not throw it out until we know that's where the problem is. A lot of work has been but into our mhonarc instal over the years to make it fit with our website etc. Dave has looked at the custom parser thing, but it's a lot more work than you'd initially think. There's a zillion corner-cases. /Magnus