Skip site navigation (1) Skip section navigation (2)

Re: Spam filtering for mailing lists

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-www(at)postgresql(dot)org
Cc: david(at)kineticode(dot)com
Subject: Re: Spam filtering for mailing lists
Date: 2006-02-01 15:48:57
Message-ID: 18691b07482f12ee88d5c054c908fbeb@biglumber.com (view raw or flat)
Thread:
Lists: pgsql-www
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>> Ummm, one thing to note, we don't have spamassassin set to auto-kill
>> anything, you have to setup some sort of filter on your end for that ...
>> with Majordomo2, we have it as an access_rule, but I don't know how to do
>> it with mailman ...

I've got it working within Mailman, and it seems to be working well: the
queue this morning has 2 spams and 1 real message, which is a vast improvement
as the old ratio was more like 70:1.

The dbdpg-commits list still seems stuck, however. I'm ccing the admin
for that list as well.

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200602011046
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8

-----BEGIN PGP SIGNATURE-----

iD8DBQFD4NgfvJuQZxSWSsgRAjrgAJoDFtpvlTVgJhEJZFwgoJgig3tXgACg/Aai
LEfNWPDs0voUizPnGYyfILU=
=7eDn
-----END PGP SIGNATURE-----



In response to

pgsql-www by date

Next:From: Magnus HaganderDate: 2006-02-01 18:18:42
Subject: Re: pgFoundry & Gborg visibility ...
Previous:From: Marc G. FournierDate: 2006-02-01 14:14:24
Subject: Re: pgFoundry & Gborg visibility ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group