Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 394192E025F for ; Tue, 11 Mar 2008 21:51:41 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 84899-02 for ; Tue, 11 Mar 2008 21:51:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id B36182E026E for ; Tue, 11 Mar 2008 21:51:38 -0300 (ADT) Received: from perhan.alvh.no-ip.org (190-95-27-98.bk17-dsl.surnet.cl [190.95.27.98]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m2C0poEB002150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Mar 2008 17:51:53 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 5DA9747BFC; Tue, 11 Mar 2008 21:51:24 -0300 (CLST) Date: Tue, 11 Mar 2008 21:51:24 -0300 From: Alvaro Herrera To: Bruce Momjian Cc: PostgreSQL www Subject: Re: Email not searchable in our archives Message-ID: <20080312005124.GD6737@alvh.no-ip.org> References: <20080311220224.GC6737@alvh.no-ip.org> <200803112211.m2BMBRl18740@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200803112211.m2BMBRl18740@momjian.us> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Tue, 11 Mar 2008 17:51:53 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/231 X-Sequence-Number: 14350 Bruce Momjian wrote: > Alvaro Herrera wrote: > > I can fix the problem by providing URLs with message ids. Would that > > help? You can find out the Message-Id trivially from the original > > email, and the URL would take you to the main message page complete with > > thread links and all. > > I have been pasting the email subject line into the search and usually > it is the first hit (when search works). I am not saying we should continue to have a broken search -- I only say that I can fix your particular use case. If you're not interested in it I can easily push the issue down in my TODO list. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support