From: Bruno Wolff III <bruno@wolff.to>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Chris <dmagick@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: UNSUBSCRIBE
Date: Wed, 10 May 2006 13:10:51 -0500
Message-ID: <20060510181051.GB11382@wolff.to> (raw)
In-Reply-To: <26504.1147238111@sss.pgh.pa.us>
References: <b8b84f110605091959s6f1a26a8md9dbf3729cd6c749@mail.gmail.com>
<44615C15.5040803@gmail.com>
<26504.1147238111@sss.pgh.pa.us>
On Wed, May 10, 2006 at 01:15:11 -0400,
Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Maybe the real problem is at the other end of the process, ie we should
> require some evidence of a greater-than-room-temp IQ to subscribe in the
> first place?
I suspect it is more lazyiness that smarts. That had to at least figure out
how to respond to the confirm message in the first place in order to get
subscribed.
My theory is that they don't want to take the trouble to figure out how to
unsubscribe when they (think that they) can just send a message to the list
(not even the admin) asking to be unsubscribed and it will (well actually won't
on these lists) happen.
Maybe posts with "unsubscribe" in the subject could be held for moderation
and/or get an automated reply with instructions for unsubscribing.
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: pgsql-performance@postgresql.org
Cc: bruno@wolff.to, tgl@sss.pgh.pa.us, dmagick@gmail.com
Subject: Re: UNSUBSCRIBE
In-Reply-To: <20060510181051.GB11382@wolff.to>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox