mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Thomas Tuttle <thinkinginbinary@gmail.com>,
	richard.dent@nhs.net, linux-kernel@vger.kernel.org
Subject: Re: [OT] Vacation message heckling (Was: Re: Richard Dent - Annual Leave)
Date: Tue, 18 Jul 2006 17:31:16 -0400	[thread overview]
Message-ID: <200607182131.k6ILVGxt004888@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 18 Jul 2006 22:30:04 +0200." <9a8748490607181330q7b7be84i3ac324d9053a5fa4@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]

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



[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2006-07-18 21:31 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 [this message]
2006-07-21  3:35       ` Craig Van Tassle
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=200607182131.k6ILVGxt004888@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.dent@nhs.net \
    --cc=thinkinginbinary@gmail.com \
    /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

all inboxes | Powered by JetHome®