From owner-freebsd-questions  Mon Mar 22 14:13:34 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from revolution.3-cities.com (revolution.3-cities.com [204.203.224.155])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1F773152A4; Mon, 22 Mar 1999 14:13:32 -0800 (PST)
	(envelope-from kstewart@3-cities.com)
Received: from 3-cities.com (kenn1018.bossig.com [208.26.241.18]) by revolution.3-cities.com (8.8.5/8.7.3) with ESMTP id OAA29557; Mon, 22 Mar 1999 14:12:25 -0800 (PST)
Message-ID: <36F6C0B8.5581E284@3-cities.com>
Date: Mon, 22 Mar 1999 14:14:16 -0800
From: Kent Stewart <kstewart@3-cities.com>
Organization: BOSSig
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Greg Black <gjb@comkey.com.au>
Cc: freebsd-questions@FreeBSD.ORG, jmb@FreeBSD.ORG
Subject: Re: Duplicate E-Mail Messages
References: <199903221651.KAA09206@iaces.com> <19990322211958.9829.qmail@alpha.comkey.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



Greg Black
wrote:
> 
> > You can get rid of these (well from your mailer) by putting in a procmail
> > filter:
> 
> We don't want to get rid of them after they arrive -- we want
> them not to be generated in the first place.  Something is
> broken out there and needs to be fixed.

What I
noticed on
the
headers
that I
looked at
was
identical
message
ID's until
hub.freebsd.org
sent the
mail on to
to
sol.net.
Then
"sarip"
and
"mail2"
got
involved
and the
duplicate
messages
appeared.
Since both
received
from
hub.freebsd.org,
the error
would
appear to
be a
FreeBSD.org
problem.

-- 
Kent
Stewart
Richland,
WA

mailto:kstewart@3-cities.com
http://www.3-cities.com/~kstewart/index.html


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message