public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Daniel Berlin" <dberlin@dberlin.org>
To: overseers@sourceware.org, jifl@jifvik.org
Subject: Re: questions about blocking disclaimers
Date: Mon, 06 Aug 2007 13:38:00 -0000	[thread overview]
Message-ID: <4aca3dc20708060638x2c39f3fcw892db0a4d76e1f3e@mail.gmail.com> (raw)
In-Reply-To: <m37io8ssh4.fsf@gossamer.airs.com>

On 06 Aug 2007 06:27:51 -0700, Ian Lance Taylor <ian@airs.com> wrote:
> Jonathan Larmour <jifl@jifvik.org> writes:
>
> > Out of interest I have had long arguments in my workplace about such
> > disclaimers, and it has been alleged that EU Data Protection law (as
> > applied in the UK at least) pretty much requires that any mail sent
> > from a business (including any employees) has to include them. It was
> > a hard fight to prevent them being added to all our email, and
> > allegedly omitting them is being done at some risk to the company
> > directors. I doubt this should change the policy, but it does show
> > that the only solution people may have is not to post from their work
> > at all, so giving them time to arrange an alternative would some
> > reasonable.
>
> I disbelieve that EU law requires you to add anything like "if you are
> not the intended recipient of this e-mail, please destroy it."  Those
> are the problematic cases for us.
>

This is my cursory understanding as well (I am not an EU law specialist).
I have seen laws in various EU countries that *do arguably require the
place of business's address be listed*, but this is really different.

> Ian
>

  reply	other threads:[~2007-08-06 13:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05  5:34 Christopher Faylor
2007-08-05 18:45 ` Christopher Faylor
2007-08-05 22:16   ` Jonathan Larmour
2007-08-05 23:54     ` Christopher Faylor
2007-08-06 10:34       ` Jonathan Larmour
2007-08-06 13:28     ` Ian Lance Taylor
2007-08-06 13:38       ` Daniel Berlin [this message]
2007-08-06 14:33       ` Gerald Pfeifer
2007-08-06 14:36       ` Jonathan Larmour

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=4aca3dc20708060638x2c39f3fcw892db0a4d76e1f3e@mail.gmail.com \
    --to=dberlin@dberlin.org \
    --cc=jifl@jifvik.org \
    --cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).