Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Repeating Messages

0 views
Skip to first unread message

Don B

unread,
Jan 15, 2001, 4:09:22 PM1/15/01
to
We have a problem with some messages coming in our IMC be delivered to the
recipient several times. Some happen every ten minutes and some are more
sporadic. Our system is Exchange5.5 just upgraded to SP4. We have tried to
what Q239420 says about removing the pointer from the Queue.dat file but
this has not resolved the issue. This problem occurred before we added SP4
and SP4 has not made any difference. The only way we can stop these messages
is to restrict the delivery of that specific sender to that recipient.
Has any one had this problem? We have been using Exchange for several years
and this started just recently.
Don Barber
System Engineer
NHS


Charles Villa

unread,
Jan 15, 2001, 4:27:04 PM1/15/01
to
I don't have any specific fixes, but have you turned on logging to see where
the extra copies are being generated? I suggest turning on SMTP protocol
logging on the IMC and message tracking on the MTA.

The problem may be at the sender's site and not yours.

Charles Villa


Ryan Schlosser

unread,
Jan 15, 2001, 7:41:47 PM1/15/01
to
yes, actually, I can say without a doubt that I'm experiencing the exact
same thing. I also followed that Q239420, and it didn't help me either. I
posted another topic (darn, wish I had seen this one first - sorry folks)
but it sounds to be an identical type of problem. I have called PSS, and
they don't have a clue what the problem is. About to call them back right
now.

dba...@nhsnet.org (Don B) wrote in <uDFvbbzfAHA.1716@tkmsftngp02>:

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----

Kirill S. Palagin

unread,
Jan 16, 2001, 12:02:08 AM1/16/01
to
It could be that some external server giving your hard time. If Ryan and Don
could post Received headers from repeating messages we could compare them and
find where problem is.

Ryan Schlosser wrote:

--
Corrections are welcome.

For "Good post" practice visit
http://members.home.com/dts-l/goodpost.htm

Kirill.


Ryan Schlosser

unread,
Jan 16, 2001, 2:07:11 PM1/16/01
to
kpal...@nomail.nomailphxint.glasnetnomail.ru (Kirill S. Palagin) wrote
in <3A63D5D0...@nomail.nomailphxint.glasnetnomail.ru>:

>It could be that some external server giving your hard time. If Ryan and
>Don could post Received headers from repeating messages we could compare
>them and find where problem is.
>

We have had the problem from four different external servers. uswest.net,
webtv.net, amazon.com, and ihighway.net. the one from uswest.net has a
file attachment. The other ones do not have file attachments.

this is one:


1/12/01 9:29:51 PM : A connection was accepted from 198.36.160.5.
1/12/01 9:29:51 PM : <<< IO: |HELO ptldpop5.ptld.uswest.net
|

1/12/01 9:29:51 PM : <<< HELO ptldpop5.ptld.uswest.net

1/12/01 9:29:51 PM : >>> 250 OK


1/12/01 9:29:51 PM : <<< IO: |MAIL FROM:<che...@netwrks.com>
|

1/12/01 9:29:51 PM : <<< MAIL FROM:<che...@netwrks.com>

1/12/01 9:29:51 PM : >>> 250 OK - mail from <che...@netwrks.com>


1/12/01 9:29:51 PM : <<< IO: |RCPT TO:<tlin...@newedgenetworks.com>
|

1/12/01 9:29:51 PM : <<< RCPT TO:<tlin...@newedgenetworks.com>

1/12/01 9:29:51 PM : >>> 250 OK - Recipient <tlin...@newedgenetworks.com>


1/12/01 9:29:51 PM : <<< IO: |DATA
|

1/12/01 9:29:51 PM : <<< DATA

1/12/01 9:29:51 PM : >>> 354 Send data. End with CRLF.CRLF


1/12/01 9:29:51 PM : <<< IO: |Received: (qmail 14170 invoked by alias); 9
Jan 2001 00:49:58 -0000
Delivered-To: fixup-t...@newedgenetworks.com@fixme
Received: (qmail 14079 invoked by uid 0); 9 Jan 2001 00:49:54 -0000
Received: from unknown (HELO curtspc) (63.227.213.110)
by 198.36.160.5 with SMTP; 9 Jan 2001 00:49:54 -0000
Message-ID: <038001c079d6$8cdf98c0$0700000a@curtspc>
From: "Curt Hedges" <che...@netwrks.com>
To: <tlin...@newedgenetworks.com>
Subject: Fw: TEVA WMB
Date: Mon, 8 Jan 2001 16:53:15 -0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_037D_01C07993.7E793540"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200

This is a multi-part message in MIME format.

------=_NextPart_000_037D_01C07993.7E793540
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: Salmon, James S (PORTLAND PL 311) <jssalmon@pcli|

1/12/01 9:29:51 PM : <<< IO: |ent.ml.com>
To: 'CurtH' <che...@netwrks.com>
Sent: Thursday, January 04, 2001 4:21 PM
Subject: TEVA WMB


> Curt -- Read up on TEVA & WMB. And let me know about CFLO.
>
> <<wmb 12-21-00>> <<TEVA 11-29-00>>
> ____________________________________________________________
>
>
>
>
> CAUTION: Electronic mail sent through the Internet is not secure and
could
> be intercepted by a third party. For your protection, avoid sending
> identifying information, such as account, Social Security or card numbers
to
> us or others. Further, do not send time-sensitive, action-oriented
> messages, such as transaction orders, fund transfer instructions, or
check
> stop payments, as it is our policy not to accept such items electronicall
>

<<< Cut out message attachment MIME stuff >>>


.
|

1/12/01 9:29:52 PM : >>> 250 OK


1/12/01 9:30:12 PM : A connection was accepted from yertle.sacweb.com.
1/12/01 9:30:12 PM : <<< IO: |HELO yertle.sacweb.com
|

1/12/01 9:30:12 PM : <<< HELO yertle.sacweb.com

1/12/01 9:30:12 PM : >>> 250 OK


1/12/01 9:30:12 PM : <<< IO: |MAIL FROM:<ho...@sacweb.net>

Arnold Babar

unread,
Jan 17, 2001, 10:49:10 AM1/17/01
to
We are experiencing the same problem. Very weird. They will come in every
10 minutes. Blocking the suspected domains from the firewall clears it up.
(Definatley not a solution.) Ours have been from smaller oraganizations
including a local ISP and a Law firm that we deal with. I spoke to someone
at the lawfirm (when the problem occurred several weeks ago). Neither of us
saw a thing. We were able to correct the problem by (drum roll) rebooting
the mail server. Once again, this is definatley not a solution.

Arnie Babar

0 new messages