From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30674 invoked by alias); 6 Aug 2007 10:34:43 -0000 Received: (qmail 30525 invoked by uid 22791); 6 Aug 2007 10:34:42 -0000 X-Spam-Check-By: sourceware.org Received: from virtual.bogons.net (HELO virtual.bogons.net) (193.178.223.136) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 06 Aug 2007 10:34:40 +0000 Received: from jifvik.dyndns.org (jifvik.dyndns.org [85.158.45.40]) by virtual.bogons.net (8.10.2+Sun/8.11.2) with ESMTP id l76AYbT09441 for ; Mon, 6 Aug 2007 11:34:37 +0100 (BST) Received: from [192.168.7.9] (unknown [87.127.20.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jifvik.dyndns.org (Postfix) with ESMTP id CC5893FE1 for ; Mon, 6 Aug 2007 11:34:36 +0100 (BST) Message-ID: <46B6F93B.70309@jifvik.org> Date: Mon, 06 Aug 2007 10:34:00 -0000 From: Jonathan Larmour User-Agent: Thunderbird 1.5.0.12 (X11/20070530) MIME-Version: 1.0 To: overseers@sourceware.org Subject: Re: questions about blocking disclaimers References: <20070805053429.GA12910@ednor.casa.cgf.cx> <20070805184604.GA14471@ednor.casa.cgf.cx> <46B64C27.102@jifvik.org> <20070805235439.GA14409@trixie.casa.cgf.cx> In-Reply-To: <20070805235439.GA14409@trixie.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00052.txt.bz2 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