Re: Proposal for change in pgsql-announce behavior

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

'k, the reply-to is easy ... the auto-unsubscribe *alot* harder ... there is an
'interface' for Mj2 that might allow for this, if someone feels up to writing
the perl hook to do it ...

I've CC'd Michael Yount into this, as he's whom I generally talk to concerning
Mj2 problems, and might have an idea of how to do this cleanly ...

Of course, this would potentially open this up to a load of attack, since its
very easy to forge an email to come from a third party ... but, setting a
Reply-To to the list-owner would make sense ...

- --On Sunday, October 29, 2006 11:53:26 -0800 Josh Berkus <josh(at)agliodbs(dot)com>
wrote:

> Marc,
>
> Right now, whenever someone posts to pgsql-announce, they get a flood of
> "Please remove me" and bounce messages. This is quite startling for vendors
> who post announcements for the first time, and quite annoying for the rest of
> us. And I think it's fixable.
>
> What if we:
>
> 1) set pgsql-announce to be "reply to pgsql-announce-reply(at)postgreSQL(dot)org".
> 2) set up pgsql-announce-reply with a set of filters which looks for
> "remove", "unsubscribe" and typical bounce messages in the body or subject of
> the reply, and unsubscibes the sender.
>
> If you can't use one list to unsubscribe another, then you can reverse it;
> have them reply to pgsql-announce, but have a seperate address
> (pgsql-announce-submit) for submitting new announcements.
>
> Thoughts?
>
> --Josh Berkus

- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy(at)hub(dot)org MSN . scrappy(at)hub(dot)org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFFRRo44QvfyHIvDvMRAhEMAKCW/3f/J0J+qNR1wQTfUK0UN31VZACeNrJz
Vj+B+FuGPb6BAVQO61INZJ8=
=Dn7D
-----END PGP SIGNATURE-----