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

Re: [HACKERS] Moderator on Committers?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-www <pgsql-www(at)postgresql(dot)org>, simon <simon(at)2ndquadrant(dot)com>, scrappy <scrappy(at)hub(dot)org>
Subject: Re: [HACKERS] Moderator on Committers?
Date: 2010-08-10 14:29:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-www
Excerpts from Tom Lane's message of mar ago 10 10:05:25 -0400 2010:
> "Greg Sabino Mullane" <greg(at)turnstep(dot)com> writes:
> > I think the spam slipped through because it was sent with a fake "from" 
> > as the address of the mailing list itself. Marc has already closed the 
> > hole per my complaint a couple of days ago. However, I think the committers 
> > list could certainly do without the "subscription hint" filter. Marc, 
> > can you disable that bit on the committers list or make me an admin 
> > for that list so I can do it myself?
> +1 ... just make sure you don't disable the "Security:" filter.
> (Possibly better would be to bypass those filters only for messages
> sourced from the CVS daemon, if that's possible.)

Possibly the script that sends the email from CVS could use the list
password somehow so that the email is automatically authorized?  (Of
course, the password must not leak from there)

Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to


pgsql-www by date

Next:From: Thom BrownDate: 2010-08-11 08:39:37
Subject: Versioning policy and pg_upgrade
Previous:From: Tom LaneDate: 2010-08-10 14:05:25
Subject: Re: [HACKERS] Moderator on Committers?

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2010-08-10 14:29:40
Subject: Re: host name support in pg_hba.conf
Previous:From: Heikki LinnakangasDate: 2010-08-10 14:29:18
Subject: Re: MERGE Specification

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