Legal disclaimers on emails to this group
Craig James <[email protected]> Fri, 6 Dec 2019 10:42:19 -0800
| Newsgroups | gmane.comp.db.postgresql.performance |
|---|---|
| Message-ID | <CAFwQ8rcEExxB8ZuE_CYj6u6FZbRZjyWn+Po31hrfLAw1uBnKMg@mail.gmail.com> |
--00000000000080c2b205990d682e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable (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 <[email protected]> wrote: > Hi, > > I am investigating a performance problem... > ... This email is non-binding, is subject to contract, and neither Kulick= e > and Soffa Industries, Inc. nor its subsidiaries (each and collectively > =E2=80=9CK&S=E2=80=9D) 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 conten= ts > 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 --00000000000080c2b205990d682e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>(I've changed the original subject, "autovac= uum locking question", of the sender's email so as not to hijack t= hat thread.)</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"= gmail_attr">On Thu, Dec 5, 2019 at 2:26 PM Mike Schanne <<a href=3D"mail= to:[email protected]">[email protected]</a>> wrote:<br></div><blockquote c= lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli= d rgb(204,204,204);padding-left:1ex"> <div lang=3D"EN-US"> <div class=3D"gmail-m_-3559226803143332119WordSection1"> <p class=3D"MsoNormal">Hi,<u></u><u></u></p> <p class=3D"MsoNormal">I am investigating a performance problem...</p></div= ><font face=3D"Arial" color=3D"Black" size=3D"2">... This email is non-bind= ing, is subject to contract, and neither Kulicke and Soffa Industries, Inc.= nor its subsidiaries (each and collectively =E2=80=9CK&S=E2=80=9D) sha= ll have any obligation to you to consummate the transactions herein or to e= nter 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 e= mail 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 consen= t of K&S is prohibited.<br> </font> </div> </blockquote></div><div><br></div>Sorry to be off topic, but this bugs me. = Language is important. This isn't directed at you specifically, but I s= ee these disclaimers all the time. How can you post to a public newsgroup t= hat automatically reproduces your email to thousands of subscribers, and ad= ditionally publishes it on publicly=C2=A0accessible archives, in direct con= flict with your company's policy appended to your email? And why on Ear= th do your company's lawyers think this sort of disclaimer is helpful a= nd even legally useful? Not to mention, do they realize it's vaguely of= fensive to every customer and colleague who receives it?<div><div><br></div= ></div><div>Craig</div></div> --00000000000080c2b205990d682e--