Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBF4OF065672 for ; Thu, 14 Dec 2000 23:24:15 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eBF4ObL10015; Thu, 14 Dec 2000 23:24:37 -0500 (EST) To: Alvar Freude cc: pgsql-sql@postgresql.org, The Hermit Hacker Subject: Re: Secure Messaging Non-Delivery Report: Re: How to represent a tree-structure in a relationaldatabase In-reply-to: <3A399963.F7A4B2C8@merz-akademie.de> References: <3A399963.F7A4B2C8@merz-akademie.de> Comments: In-reply-to Alvar Freude message dated "Fri, 15 Dec 2000 05:09:07 +0100" Date: Thu, 14 Dec 2000 23:24:37 -0500 Message-ID: <10012.976854277@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200012/156 X-Sequence-Number: 490 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@hub.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