On Tue, May 7, 2019 at 2:07 PM Anders Andersson <pipat...@gmail.com> wrote: > > ...[snip]...
What they probably did not realize is that the OpenBSD foundation is openbsdfoundation.org and not openbsd.org, so for the nature of their e-mail message, the To: domain is going to tech@openbsd.org of the OpenBSD Project, but they were trying to find someone at the OpenBSD Foundation, instead. And by definition all information contained in e-mail messages sent to tech@openbsd.org nearly instantly became public information, since any of the thousands of people who use OpenBSD or discuss its development subscribed who are subscribed to this technical discussion mailing list will have already received any message. "tech@openbsd.org - Discussion of technical topics for OpenBSD developers and advanced users." " This communication contains information that may be c.... If you have received this communication in error, please immediately... " Such generic language as that at the footer of an e-mail has no weight or affect on the content made public by the sender choosing an inherently-public To: address, and is spurious and especially annoying to have such spurious disclaimer within normal correspondence, but doubly so, when posting to public mailing lists such as tech@openbsd.org Obviously, the sender of an e-mail cannot command the deletion of an e-mail message in any case, AFTER they have already sent it in any case, which isn't even possible for many recipients that permanently and automatically archive every e-mail message received (and the original message will likely appear in publicly accessible mailing list archives). The burden of correct delivery is on the sender of an e-mail communication to verify their To: address list is 100% correct, before instructing their e-mail software to send that message. Even then, it is readily apparent from the e-mail related IETF standards which give the basic operation of internet email protocols such as SMTP: That the security or privacy of a message content is not assured and cannot reasonably be relied upon when e-mail is sent traversing internet-connected systems, and the use of an additional encryption solution such as PGP or GNUpg would be necessary to encrypt and secure the information PRIOR to placing into an e-mail message, in order to have a chance at adequately preventing potential display or logging of a sensitive or confidential e-mail message body to all potentially unauthorized 3rd parties: with at least a minimal level of security reliability.. > > On Tue, May 7, 2019 at 12:47 PM Lipinska, Sara > <sara.lipin...@hireright.com> wrote: > > > > HireRight Limited is a limited liability company incorporated in England > > (registered number 4036193) whose registered office is at Gun Court, 70 > > Wapping Lane, London, E1W 2RD. > > > > This communication contains information that may be confidential, > > proprietary in nature, and may also be attorney-client privileged and/or > > work product privileged. It is for the exclusive use of the intended > > recipient(s). If you are not the intended recipient(s) or the person > > responsible for delivering it to the intended recipient(s), please note > > that any form of dissemination, distribution or copying of this > > communication is strictly prohibited and may be unlawful. If you have > > received this communication in error, please immediately notify the sender > > by replying to this message and delete this e-mail immediately. Thank you > > for your cooperation. Please be advised that neither HireRight, its > > affiliates, its employees or agents accept liability for any errors, > > omissions or damages caused by delays of receipt or by any virus infection > > in this message or its attachments, or which may otherwise arise as a > > result of this e-mail transmission. > > It's not polite to post legal threats. If you don't want people to > disseminate, distribute or copy what you write, you should probably > not send it out to a mailing list. > Regards, -- -JH
