| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvar Freude <alvar(dot)freude(at)merz-akademie(dot)de>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Secure Messaging Non-Delivery Report: Re: How to represent a tree-structure in a relationaldatabase |
| Date: | 2000-12-15 04:39:39 |
| Message-ID: | Pine.BSF.4.21.0012150039120.453-100000@thelab.hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
oh, wait, you didn't want me to remove dana from all lists? :) if
offensive on one, I figure its offensive on all ... saves time, no?
On Thu, 14 Dec 2000, Tom Lane wrote:
> As of a few moments ago, Dana Reed is an ex-subscriber to pgsql-general.
> Evidently he/she is about to be an ex-subscriber to pgsql-sql as well.
>
> Most mailing list admins take a very dim view of mail software that
> sends bounces to the original author of a mailing-list message, rather
> than to the mailing list's errors address (the "envelope sender" in SMTP
> parlance). I don't run the pgsql lists myself, but on lists I do run,
> bouncing to authors who can't do anything about it is grounds for
> instant removal from the list. I believe Marc feels the same. If you
> get bounces from third-party recipients of pgsql list messages, let Marc
> know (scrappy(at)hub(dot)org). There's no point in bothering the rest of the
> list with it, though --- Marc is the only one in a position to do
> anything about it.
>
> regards, tom lane
>
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvar Freude | 2000-12-15 04:58:23 | Re: Secure Messaging Non-Delivery Report: Re: How to representa tree-structure in a relationaldatabase |
| Previous Message | Tom Lane | 2000-12-15 04:24:37 | Re: Secure Messaging Non-Delivery Report: Re: How to represent a tree-structure in a relationaldatabase |