From owner-freebsd-chat Sat Jan 6 20:38:47 2001 Delivered-To: freebsd-chat@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id 3961237B402 for ; Sat, 6 Jan 2001 20:38:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f074cNs89388; Sat, 6 Jan 2001 22:38:23 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101070438.f074cNs89388@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Rob Snow (Lists)" Cc: freebsd-chat@FreeBSD.ORG Subject: Re: Hmm, dupes? In-Reply-To: Message from "Rob Snow (Lists)" of "Sat, 06 Jan 2001 06:49:06 CST." <021101c077df$0e72f0c0$2100000a@dympna.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Jan 2001 22:38:23 -0600 From: David Kelly Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Rob Snow (Lists)" writes: > Is anyone else seeing LOTS of dupes on -questions, -chat, etc? I just > re-subscribed due to some flaky DNS issues and am seeing 60% dupes on > messages...I wish it were 100% or 0%, that would be much easier to solve. > which lists@dympna.com shows only single entries. If the messages are spawning in the delivery stage the duplicates will have the same Message-ID: header. Several ways to deal with that but I use "slocal -suppressdup" out of the nmh package. Procmail has ways too. Well, no, actually I don't quite. I don't use the -suppressdup flag as I hacked the source and made that the default. Such is what source code is good for. If you use this technique on your account, you'll have to zero ~/.maildelivery.db every now and then. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message