public inbox for [email protected]  

help / color / mirror / Atom feed

From: Stefan Kaltenbrunner <[email protected]>
To: Tom Lane <[email protected]>
Cc: Dave Page <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: A plague of link spam ...
Date: Sat, 16 Mar 2013 20:09:51 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-www>

On 03/16/2013 07:56 PM, Tom Lane wrote:
> Dave Page <[email protected]> writes:
>> On 16 Mar 2013, at 18:34, Stefan Kaltenbrunner <[email protected]> wrote:
> 
>>> On 03/15/2013 09:46 PM, Tom Lane wrote:
>>>> Stefan Kaltenbrunner <[email protected]> writes:
>>>>> On 03/15/2013 07:16 PM, Tom Lane wrote:
>>>>>> (I am only about one or two more spams away from
>>>>>> summarily blocking all yahoo traffic from my own mail server, btw.
>>>>>> They account for easily a third of all the spam I'm seeing lately.)
> 
>>> However - I still don't think we can seriously consider blocking all of
>>> yahoo inbound - what do others think about this?
> 
>> Sooner or later someone has to make a stand. 
> 
> TBH I wasn't (very) seriously suggesting we institute such a block on
> the project's mailing lists, only remarking that I was about ready
> to do so for my own mail.  But I'm well known for having draconian
> filtering in place.
> 
> What I *would* like to see on the lists is some attempt at catching
> link spam, because more and more of that has been getting through
> lately.  I'm not sure all of it has been from yahoo accounts.

working on it, spent a few hours yesterday and today to work on our
filtering but it is not as easy as simply declaring "everything that is
a very short mail and has a url in it is bad".
We do have regular mailbox users (in the same namespaces as the list) as
do we have lists that want to receive such stuff (say the sysadmin list
getting an email about a failed http download from a cronjob with
basically just the url).


Stefan


-- 
Sent via pgsql-www mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www

view thread (15+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: A plague of link spam ...
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox