Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3C3449FB349 for ; Tue, 12 Jun 2007 19:08:47 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 19698-05 for ; Tue, 12 Jun 2007 19:08:40 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.236]) by postgresql.org (Postfix) with ESMTP id B9ADD9FA2D7 for ; Tue, 12 Jun 2007 19:08:40 -0300 (ADT) Received: by wx-out-0506.google.com with SMTP id h28so732wxd for ; Tue, 12 Jun 2007 15:08:39 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=e9wHIavYaGtoK2sYN6fgAhC0JGuyI7u1sxTsD51FG9BJ/R7Leg8C6gKxW3iTuVmWYsGOb0SJM8qi0utrZ6Ts35k+zs2/qwUQQ94cBham9E/Dq6gaI1t6TZgRetmZIEUaPfxSobaUHi8POOH77ZhCNrPs52/6fVnEkIftVXb/S7A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qACOoN85C4KmQdJqQk7Oa1Ug3EX4nelAhe/chWdqxiV0B6yo+FQ74IjgEYUfO2XQYYs2RgQ4Ye+HASX31WTYEpPY0SDaNH9RfPeCIgzzG/au6sCsToOyNPw8k4DzhlVWaREv4eEZLMlvfk6TAB0crmXaj1CtCwA9DGOB86eykjE= Received: by 10.70.87.11 with SMTP id k11mr11033744wxb.1181686119555; Tue, 12 Jun 2007 15:08:39 -0700 (PDT) Received: by 10.70.43.9 with HTTP; Tue, 12 Jun 2007 15:08:39 -0700 (PDT) Message-ID: <5a0a9d6f0706121508j31e43fa3te2731059858d097a@mail.gmail.com> Date: Tue, 12 Jun 2007 15:08:39 -0700 From: "Andrew Hammond" To: "Tom Lane" Subject: Re: [HACKERS] Avoiding legal email signatures Cc: "Dave Page" , "Josh Berkus" , pgsql-hackers@postgresql.org, pgsql-www@postgresql.org In-Reply-To: <26489.1181680195@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200706092214.l59ME0i06348@momjian.us> <20070610180414.GQ23679@phlogiston.dyndns.org> <200706121304.13914.josh@agliodbs.com> <466EFF73.9080100@postgresql.org> <26489.1181680195@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/61 X-Sequence-Number: 12100 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 6/12/07, Tom Lane wrote: > A more serious objection is that any automated tool would probably get it > wrong sometimes, and strip important text. > > > I vote 'lets not bother' > > Right. I agree with Josh's idea about mentioning list policies in the > subscription confirmation message, though. Why? If the legal mumbo-jumbo has already got some precedence as being un-enforcable (even if it's only in a handful of jurisdictions), why give it even a patina of credibility by addressing it in a policy? Saying that it's not applicable here implies that is is applicable elsewhere. To quote Ghandi "first they laugh at you, then they ignore you, then they fight you, then you win." I say we stick with the laughing. To that end, I propose should have a policy about being pelted with scathing sarcasm when the signal to boilerplate ratio drops below 10:1. Andrew -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGbxln+zlEYLc6JJgRAuaNAJsECSRrgIqR1f5c15P7OszVa34lVgCghWSb io55WHyChKGQVHCQ9R+z2ec= =KNyQ -----END PGP SIGNATURE-----