X-Original-To: pgsql-www-postgresql.org@postgresql.org
Received: from localhost (wm.hub.org [200.46.204.128])
	by postgresql.org (Postfix) with ESMTP id C4E609FB354;
	Sat,  5 Aug 2006 15:51:46 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024)
	with ESMTP id 62775-01; Sat,  5 Aug 2006 18:51:42 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from davinci.ethosmedia.com (server227.ethosmedia.com
	[209.128.84.227])
	by postgresql.org (Postfix) with ESMTP id 63E039FB34F;
	Sat,  5 Aug 2006 15:51:42 -0300 (ADT)
X-EthosMedia-Virus-Scanned: no infections found
Received: from [63.195.55.98] (account josh@agliodbs.com HELO
	spooky.sf.agliodbs.com)
	by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP id 9884281; Sat, 05 Aug 2006 11:55:02 -0700
From: Josh Berkus <josh@agliodbs.com>
Organization: PostgreSQL @ Sun
To: pgsql-www@postgresql.org
Subject: Re: Maia Mailgard down?
Date: Sat, 5 Aug 2006 11:52:03 -0700
User-Agent: KMail/1.8.2
Cc: "Marc G. Fournier" <scrappy@postgresql.org>
References: <44CA99D2.6070102@agliodbs.com>
	<20060728221623.B1188@ganymede.hub.org>
	<200607311222.12535.josh@agliodbs.com>
In-Reply-To: <200607311222.12535.josh@agliodbs.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200608051152.03188.josh@agliodbs.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=FORGED_RCVD_HELO
X-Spam-Level: 
X-Archive-Number: 200608/29
X-Sequence-Number: 10420

Folks,

Is there any way we can return to whatever we were using before Maia mailgard?   
Maia is patently NOT working ... it's fundamentally broken in some way, and 
isn't blocking any spam.  The interface for Baysian filtering is also awkward 
and darned near unusable.  In a couple months we're going to be trying to do 
the PostgreSQL 8.2 release which means that we need the @postgresql.org 
e-mail addresses working ... and right now they're all receiving a flood of 
unfiltered spam, making them unusable.

-- 
Josh Berkus
PostgreSQL @ Sun
San Francisco