From: Tim Cross <theophilusx@gmail.com>
To: pgsql-performance@lists.postgresql.org
Cc: Mike Schanne <mschanne@kns.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Legal disclaimers on emails to this group
Date: Sat, 07 Dec 2019 09:42:54 +1100
Message-ID: <87v9qtjcsx.fsf@gmail.com> (raw)
In-Reply-To: <CAFwQ8rcEExxB8ZuE_CYj6u6FZbRZjyWn+Po31hrfLAw1uBnKMg@mail.gmail.com>
References: <0871fcf35ceb4caa8a2204ca9c38e330@USEPRDEX1.corp.kns.com>
<CAFwQ8rcEExxB8ZuE_CYj6u6FZbRZjyWn+Po31hrfLAw1uBnKMg@mail.gmail.com>
Craig James <cjames@emolecules.com> writes:
> (I've changed the original subject, "autovacuum locking question", of the
> sender's email so as not to hijack that thread.)
>
> On Thu, Dec 5, 2019 at 2:26 PM Mike Schanne <mschanne@kns.com> wrote:
>
>> Hi,
>>
>> I am investigating a performance problem...
>> ... This email is non-binding, is subject to contract, and neither Kulicke
>> and Soffa Industries, Inc. nor its subsidiaries (each and collectively
>> “K&S”) shall have any obligation to you to consummate the transactions
>> herein or to enter into any agreement, other than in accordance with the
>> terms and conditions of a definitive agreement if and when negotiated,
>> finalized and executed between the parties. This email and all its contents
>> are protected by International and United States copyright laws. Any
>> reproduction or use of all or any part of this email without the express
>> written consent of K&S is prohibited.
>>
>
> Sorry to be off topic, but this bugs me. Language is important. This isn't
> directed at you specifically, but I see these disclaimers all the time. How
> can you post to a public newsgroup that automatically reproduces your email
> to thousands of subscribers, and additionally publishes it on
> publicly accessible archives, in direct conflict with your company's policy
> appended to your email? And why on Earth do your company's lawyers think
> this sort of disclaimer is helpful and even legally useful? Not to mention,
> do they realize it's vaguely offensive to every customer and colleague who
> receives it?
>
> Craig
Oh how I hear you!
This is what I was using as my email signature (but not for groups). I
feel for the OP who probably has little choice (other than work for a
different employer, which is a very valid choice given the 'organisational
culture' exhibited by policies requiring such nonsense)
Notice to all senders:
If you send me a message, on receipt of that message I consider that message to
be my property and I will copy, share and deceminate as I see fit. I will
provide attribution when appropriate and I willl endeavour to comply with all
reasonable requests. However, I reject all threats or implied threats of legal
action arising from an error or mistake on your part. It is your responsibility
to manage your communications appropriately, not mine.
--
Tim Cross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: theophilusx@gmail.com, pgsql-performance@lists.postgresql.org, mschanne@kns.com
Subject: Re: Legal disclaimers on emails to this group
In-Reply-To: <87v9qtjcsx.fsf@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox