public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: overseers@sources.redhat.com
Subject: Re: Confidentiality notices
Date: Wed, 28 Jan 2004 16:39:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.58.0401281735480.39845@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20040128161742.GB25439@redhat.com>

On Wed, 28 Jan 2004, Christopher Faylor wrote:
> On Wed, Jan 28, 2004 at 10:04:22AM -0500, Ian Lance Taylor wrote:
>> I've noticed several e-mails recently with confidentiality notices
>> which we are violating when we archive the message on the web site.
>>
>> Any thoughts on whether we should check for these notices on incoming
>> mail, and bounce them back to the sender?

Yes, please!  Less for legal reasons, than to make a statement.

> I've suggested that in the past.  This is one of the reasons that I
> modified the sources.redhat.com mailing list web page to mention the
> fact that the lists are archived.  I don't know of gcc.gnu.org has any
> wording to this effect, though.

http://gcc.gnu.org/lists.html has

  Please do not include or reference confidentiality notices, like:

    The referring document contains privileged and confidential
    information. If you are not the intended recipient you must not
    disseminate, copy or take any action in reliance on it, and we request
    that you notify companyname immediately.

  Such disclaimers are inappropriate for mail sent to public lists. If
  your  company automatically adds something like this to outgoing mail,
  and you can't convince them to stop, you might consider using a free
  web-based e-mail account.

> Once we do that, I could easily start bouncing messages which contain
> confidentiality trailers. FWIW, I really hate them.

Feel free to start doing so for the GCC lists right away, at least as
far as I'm concerned. ;-)  Unconditionally.

Gerald
-- 
Gerald Pfeifer (Jerry)   gerald@pfeifer.com   http://www.pfeifer.com/gerald/

  reply	other threads:[~2004-01-28 16:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28 15:04 Ian Lance Taylor
2004-01-28 16:17 ` Christopher Faylor
2004-01-28 16:39   ` Gerald Pfeifer [this message]
2004-01-28 18:08     ` Christopher Faylor
2004-01-28 18:18       ` Gerald Pfeifer
2004-03-01 22:21         ` Gerald Pfeifer
2004-01-28 16:28 ` fche
2004-01-28 16:40   ` Ian Lance Taylor

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=Pine.BSF.4.58.0401281735480.39845@acrux.dbai.tuwien.ac.at \
    --to=gerald@pfeifer.com \
    --cc=overseers@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).