From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16250 invoked by alias); 24 May 2003 03:50:10 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 16211 invoked from network); 24 May 2003 03:50:09 -0000 Received: from unknown (HELO dberlin.org) (69.3.5.6) by sources.redhat.com with SMTP; 24 May 2003 03:50:09 -0000 Received: from [192.168.1.3] (account dberlin HELO dberlin.org) by dberlin.org (CommuniGate Pro SMTP 4.1b6) with ESMTP-TLS id 4059793; Fri, 23 May 2003 23:50:09 -0400 Date: Sat, 24 May 2003 03:57:00 -0000 Subject: Re: A few suggestions for bugzilla mail to gcc-bugs Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: gcc@gcc.gnu.org To: DJ Delorie From: Daniel Berlin In-Reply-To: <200305240305.h4O350922816@greed.delorie.com> Message-Id: Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg02175.txt.bz2 On Friday, May 23, 2003, at 11:05 PM, DJ Delorie wrote: > >> Yes, but i can't automate people doing the right thing. > > How about a procmail rule? Funny you mention, when i sugggested a procmail rule to chris for handling mail to gcc-gnats, so that i didn't have to handle it in the script, he said handling it in the script would be much easier than trying to get qmail to run procmail and do this, etc. > If gcc-bugs gets mail and sees > To:.*gcc-bugzilla in the headers, it silently discards the email. > > Assuming gcc-bugs uses procmail, of course. > It doesn't, it uses qmail + something else. --Dan