| From: | expect <expect(at)ihubbell(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | This mail list and its policies |
| Date: | 2003-09-19 03:59:53 |
| Message-ID: | 20030918205953.6334a8e7.expect@ihubbell.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I had no idea that my address was being broadcast to the world via
comp.databases.postgresql.general I have no problem with having messages sent
to the list go to the group. I do have a problem with my address out there in
the free and clear. Shouldn't the initial subscription notice let new sub-
scribers know that their address will be broadcast over the planet?
What's the logic and/or justification for doing this? I can handle the spam
using the delete key but I really don't like the additional burden that it
puts on my ISP. I would have posted via usenet had I known about this policy.
As a matter of fact that's what I intend to do from now on. Well this
address was good for some time and now it's tainted. The list owner
should send out as part of the pre-subscription message a warning that
the address they use will show up on usenet and the www.
Things that should be done as a responsible list:
1. warning in the pre-subscription notice about broadcasting the address
2. option to hide the sender, from addresses and any other address except
pgsql-general(at)postgresql(dot)org and any address that's in the body.
3. don't allow bcc to the list and don't forward messages to
info(at)postgresql(dot)org to the list.
I wonder how many subscribers to the list know that their address is
"out there" now? I suppose many have found out recently.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-09-19 04:21:25 | Re: Sequences |
| Previous Message | Andrew Rawnsley | 2003-09-19 03:35:08 | Sequences |