From: Jonathan Larmour <jifl@jifvik.org>
To: overseers@sourceware.org
Subject: Re: questions about blocking disclaimers
Date: Mon, 06 Aug 2007 10:34:00 -0000 [thread overview]
Message-ID: <46B6F93B.70309@jifvik.org> (raw)
In-Reply-To: <20070805235439.GA14409@trixie.casa.cgf.cx>
Christopher Faylor wrote:
> On Sun, Aug 05, 2007 at 11:16:07PM +0100, Jonathan Larmour wrote:
>> My only thought is that this might be sudden and dramatic for some
>> people, who may find it difficult to remove them. Can it temporarily
>> accept the message (with a warning that they will be rejected entirely
>> soon), and after a month, we change it so we do reject them?
>
> fche suggested this, too. It will be a little extra work to warn people
> while also accepting the message but it is doable. In fact, I wonder if
> that just shouldn't be the default from now on. It would be pretty
> irritating to receive this message every time you send email.
True!
> The only problem with allowing them but complaining to the sender is
> that it would be harder to figure out when one slipped by the filter.
> The fact that something hit the disclaimer filter shows up in syslog
> output now but there is no way to know when something should have been
> caught but wasn't.
If we're prepared to reject them, it doesn't seem any worse to maybe modify
the body - add a little something at the top? Maybe Something like:
[ From the sourceware/gcc.gnu.org mail system: this message appears to
contain a company disclaimer or confidentiality notice, which is against
site policy. Please ensure the sender corrects this. ]
Jifl
--
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next prev parent reply other threads:[~2007-08-06 10:34 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 [this message]
2007-08-06 13:28 ` Ian Lance Taylor
2007-08-06 13:38 ` Daniel Berlin
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=46B6F93B.70309@jifvik.org \
--to=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).