From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1172 invoked by alias); 18 Nov 2005 19:25:59 -0000 Received: (qmail 1164 invoked by uid 22791); 18 Nov 2005 19:25:56 -0000 Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 18 Nov 2005 19:25:56 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 6A94D48CFC4; Fri, 18 Nov 2005 14:25:54 -0500 (EST) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14007-01-4; Fri, 18 Nov 2005 14:25:54 -0500 (EST) Received: from takamaka.act-europe.fr (s142-179-108-108.bc.hsia.telus.net [142.179.108.108]) by nile.gnat.com (Postfix) with ESMTP id 1729B48CDA1; Fri, 18 Nov 2005 14:25:54 -0500 (EST) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 9F95447E79; Fri, 18 Nov 2005 11:25:52 -0800 (PST) Date: Fri, 18 Nov 2005 19:25:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: pgilliam@us.ibm.com, gdb@sourceware.org, cagney@gnu.org, jtc@acorntoolworks.com, fnf@ninemoons.com, Peter.Schauer@regent.e-technik.tu-muenchen.de, ezannoni@redhat.com Subject: Re: Maintainer policy for GDB Message-ID: <20051118192552.GV1635@adacore.com> References: <20051117044801.GA4705@nevyn.them.org> <20051117231020.GJ1635@adacore.com> <200511180956.14917.pgilliam@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00400.txt.bz2 > I don't know of any technological solution, except to configure the > list server to filter addresses in order to prevent multiple messages. > Most mailing lists don't do that, and FWIW I'm used to have double > messages, they don't annoy me. That's why I cannot understand why > people bother to use Mail-Followup-To. IMHO it causes more trouble > than it's worth. I was going to answer Eli privately about this, but maybe it's going to be useful to others too, so here is a small suggestion. You know that emails all have a message ID that is unique to the email. The same email sent to a mailing list and an individual will have the same message ID. So you can use that to filter out doubles. Here is a procmail recipe that does just that: # The following 2 rules will avoid e-mail duplicates (these duplicates # are stored in the duplicates folder instead). :0Wch:.messageid.lock | formail -D 32768 .messageid.cache :0a: duplicates -- Joel