Date: Fri, 8 Jun 2007 12:04:04 -0400
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-www@postgresql.org
Subject: Re: various spam
Message-ID: <20070608160404.GO17144@phlogiston.dyndns.org>
References: <20070608143339.GC17144@phlogiston.dyndns.org>
	<A6DD7A48B064B4EC073889AB@ganymede.hub.org>
	<4669794C.6030307@commandprompt.com>
	<20070608155036.GN17144@phlogiston.dyndns.org>
	<46697C05.5080408@commandprompt.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46697C05.5080408@commandprompt.com>
User-Agent: Mutt/1.5.9i

On Fri, Jun 08, 2007 at 08:55:49AM -0700, Joshua D. Drake wrote:
> Is there not some standard keywords within the post that we can block?

We're already getting sort of bitten by this; so I'd sort of prefer
not.  If these messages don't set off whatever antispam system we've
in place (and we must have one, because I don't see _that_ much spam
in the stuff I have to moderate), then I think the processing will be
too costly.

> Or even a specific phrase? Or block the email addresses?

I'll have a look at the email addresses and see if they're
consistent.  They're often forged, though.

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca
I remember when computers were frustrating because they *did* exactly what 
you told them to.  That actually seems sort of quaint now.
		--J.D. Baldwin