Content-Type: text/plain; charset=UTF-8
Cc: Greg Sabino Mullane <greg@turnstep.com>, w^3 <pgsql-www@postgresql.org>
Subject: Re: Stopping link spam on the lists
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Magnus Hagander <magnus@hagander.net>
In-reply-to: 
 <CABUevEyLXSAOEBLa4SFUm9pB_470wVgG4sUEKyfd9SVhU5yxEQ@mail.gmail.com>
References: <16170.1333746317@sss.pgh.pa.us>
	<c38808b085b1897dc873e6c36f2e140d@biglumber.com>
	<CABUevEyLXSAOEBLa4SFUm9pB_470wVgG4sUEKyfd9SVhU5yxEQ@mail.gmail.com>
Date: Sat, 07 Apr 2012 21:32:25 -0300
Message-Id: <1333845038-sup-6474@alvh.no-ip.org>
User-Agent: Sup/git
Content-Transfer-Encoding: quoted-printable


Excerpts from Magnus Hagander's message of s=C3=A1b abr 07 13:59:57 -0300=
 2012:
> On Sat, Apr 7, 2012 at 18:55, Greg Sabino Mullane <greg@turnstep.com> w=
rote:

> > Of course, as usual, all of this talk is pretty pointless as the
> > main person who should be involved here, Marc, is not subscribed
> > to -www, last I heard. :(
>=20
> He's not, but our incoming email no longer passes through the hub.org
> antispam, and Alvaro has a decent clue on how the remaining pieces are
> stitched together. (Work in progress to clean it up further, of
> course, just currently on hold as alvaro has been  busy with the CF
> work)

The remaining question, in my mind, is: is there a way to reliably
detect that link spam is just link spam and reject it altogether in
Spamassassin?  If that's the case, then we could do it at that level and
save the work downstream.  This is something that Stefan would have to
answer.

--=20
=C3=81lvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support