Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 469B49FA28D; Tue, 12 Jun 2007 17:03:40 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 64039-02; Tue, 12 Jun 2007 17:03:27 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from davinci.ethosmedia.com (server227.ethosmedia.com [209.128.84.227]) by postgresql.org (Postfix) with ESMTP id C8AD39FA4F0; Tue, 12 Jun 2007 17:03:29 -0300 (ADT) X-EthosMedia-Virus-Scanned: no infections found Received: from [63.195.55.98] (account josh@agliodbs.com HELO [192.168.2.3]) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 12381873; Tue, 12 Jun 2007 13:07:38 -0700 From: Josh Berkus Organization: PostgreSQL @ Sun To: pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Avoiding legal email signatures Date: Tue, 12 Jun 2007 13:04:13 -0700 User-Agent: KMail/1.8.2 Cc: pgsql-www@postgresql.org References: <200706092214.l59ME0i06348@momjian.us> <20070610180414.GQ23679@phlogiston.dyndns.org> In-Reply-To: <20070610180414.GQ23679@phlogiston.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200706121304.13914.josh@agliodbs.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/54 X-Sequence-Number: 12093 All, > Perhaps we make a policy that corporate-style ("disclaimered") mail > is encouraged to seek support via corporate-style channels (e.g. is > pointed at the commercial support companies). =A0I'm uncomfortable with > such a policy, but it'd be better than "ignore these nasty corporate > victims", which is what the proposal so far sounds like to me. =46irst off, I'm not clear on why we're discussing this on -hackers; -www w= ould=20 be the appropriate list. So I'm cross posting; please reply any additional= =20 messages to -www. Second, I'm not sure why we care. I don't believe that e-mail confidential= ity=20 notices are in fact enforceable, or at least they haven't been in some=20 high-profile cases which made the news. IANAL, of course. However: > Haven't we been over this at least once before? Greg is right, just > document the point and leave it alone. If you want to get really picky > about, make the confirmation email from the subscription process > specifically state that confirming subscription is an acceptance of the > PostgreSQL.Org usage policies which can be found here (insert link). This is a good idea anyway. We should have a list usage policy, and we sho= uld=20 link to if from the subscribe confirmation and from the web subscription=20 page. In addition to letting people know that e-mail confidentiality foote= rs=20 will be ignored, we can tell them how the lists are moderated, how to=20 unsubscribe (can't have this in enough places), not to use HTML mail, etc. So, who wants to write it? The only additional idea I have is that we ought to simply strip away any=20 e-mail footer over 4 lines from the archives. Not only would this purge t= he=20 confidentiality footers, it would save us some space in general. =2D-=20 Josh Berkus PostgreSQL @ Sun San Francisco