From: Craig Van Tassle <craig@codestorm.org>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Vacation message heckling (Was: Re: Richard Dent - Annual Leave)
Date: Thu, 20 Jul 2006 22:35:17 -0500 [thread overview]
Message-ID: <44C04B75.6030106@codestorm.org> (raw)
In-Reply-To: <200607182131.k6ILVGxt004888@turing-police.cc.vt.edu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Wow relax. I've seen in may placed of employment that ALL emails send out have
the disclaimer on them and he may not be able to help it.
What I really think is bad is that he actually left his out-of-office agent
running for LKML.
Valdis.Kletnieks@vt.edu wrote:
> On Tue, 18 Jul 2006 22:30:04 +0200, Jesper Juhl said:
>
>> Claiming anything send by email is confidential seems completely
>> rediculous to me.
>
> There actually *is* a valid usage case for these disclaimers in *some* cases.
>
> If there *is* in fact material covered by lawyer-client or similar privilege,
> having the disclaimer on *those items alone* can do some good when the other
> side's legal eagles subpoena all e-mails with the phrase 'Project Wombat'
> in them - it puts the other side on notice that they shouldn't be looking
> at that item and it should be returned.
>
> It's the same legal theory as subpoenaing all the paper documents, and finding
> in the 53 boxes, a sheet stamped 'Privileged and Confidential' that
> accidentally got into box 27 - there's strict rules about what happens then.
>
> Of course, paper documents are stamped on the TOP so you stop reading, and
> not all of them are stamped... :)
>
> (And I actually did at one time have dealings with a lawyer who Actually Got
> It. E-mails re: scheduling and other administrivia didn't have a disclaimer,
> stuff that was actually sensitive had a very short one at the *top*...)
>
>> Perhaps if the email was encrypted I could attach some weight to a
>> disclaimer like thatt, but sending unencrypted email is like writing on
>> the back of a postcard - it can be read by a huge number of people in
>> transit - admins managing the mail servers where it is stored along
>> the way, people sniffing traffic on the lines it passes through,
>
> At least in the US, the law says otherwise. 18 USC 2511 basically says
> that the admins aren't allowed to blab, and the traffic sniffers are
> committing a crime already.
>
> http://www.law.cornell.edu/uscode/html/uscode18/usc_sec_18_00002511----000-.html
>
> And if you catch them at it, 18 USC 2520 says you can sue them for damages:
>
> http://www.law.cornell.edu/uscode/html/uscode18/usc_sec_18_00002520----000-.html
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEwEtuAOTIJ89W4sIRAqeGAJ4zI/kIbei66bOAHglhrEsD06YBTQCgxGf+
8NoBLMHK1wTVebcH+Nb7Wmc=
=DrJq
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-07-21 3:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 8:06 Richard Dent - Annual Leave Dent Richard
2006-07-18 13:27 ` [OT] Vacation message heckling (Was: Re: Richard Dent - Annual Leave) Thomas Tuttle
2006-07-18 14:43 ` Valdis.Kletnieks
2006-07-18 20:04 ` Hans-Peter Jansen
2006-07-18 20:30 ` Jesper Juhl
2006-07-18 21:31 ` Valdis.Kletnieks
2006-07-21 3:35 ` Craig Van Tassle [this message]
2006-07-21 11:31 ` Valdis.Kletnieks
2006-07-18 22:04 ` Jan Engelhardt
2006-07-19 9:14 ` Erik Mouw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44C04B75.6030106@codestorm.org \
--to=craig@codestorm.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox