Leslie
Well, SP4 contains an interesting change: It will store only one copy
of a message no matter how many times it's received if the Message-ID
is the same. I.e., only unique messages are stored.
Based on that, I'd ask if this was happening on both servers, or only
on the SP3 server. If it's only on the SP3 server then the messages
are the same ones, received over and over. If it's happening on both
servers the messages are unique and the problem lies on the
transmitting server.
------------------
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Rich Matheisen [MVP] <rich...@rmcons.com.NOSPAM.COM> wrote in message
news:3gh5atsjnq76pt2o5...@4ax.com...
>Thanks for responding.
>Today it is happening to an account on one of the Exchange 5.5 SP3 and
>Exchange 5.5 SP4 servers.
And you checked the message-ids on the messages? Were they different
or the same?
>A couple of weeks ago it happened to my Exchange
>2000 account. For one week I got repeated messages from two sources. They
>both appeared on Monday and they both stopped on Sunday (within hours of
>each other). I emailed both senders and asked to have the emails stopped.
>One sender was Winguides and I did get an "unsubscribe" notification. The
>other sender was a little more difficult to pin down. I was surprised (and
>pleased) to see both messages stop, however, other users reported receiving
>repeated emails during the week. Blocking helped, but I considered that a
>bandaid to what is becoming a chronic problem. I am on hold to Microsoft
>right now- just wondering if there are any answeres to this one. I can't
>have users getting repeated emails every 30 minutes for a week, especially
>my executive staff- they will be at my throat!!
If the messages are coming directly to you from the source then use
SMTP Protocol Logging or Message Archival to investigate further. If
it's not your server that's the problem then MS isn't going to be of
much help.
If you get your mail from your ISP, using ETRN, then the ISP's SMTP
server may be the problem.
If you're using <shudder> once of those POP3-to-SMTP things then
that's where I'd be looking. They're notorious for this sort of
behavior!
Vlastimil
"Rich Matheisen [MVP]" <rich...@rmcons.com.NOSPAM.COM> skrev i melding
news:rkr5atk8om90cf43t...@4ax.com...
I hope this helps.
"Vlastimil Schart" <vlastimi...@arcus.no> wrote in message
news:4tKo6.7603$t21.1...@news3.oke.nextra.no...
Our environment:
Mail comes in on an Exchange Server SP4 System. (One Mail)
Mail is redirected to another Location (through a Custom Recipient Entry).
Mail leaves the Exchange Server. (Here starts the point where the Mails
duplicate)
Mail is delivered multiple times to the Destination Sendmail System (till
NDR is created through the Exchange System).
In the Sendmail-Logfiles:
After sending the "." (which identifies the end of the Mail) the
Exchange-System sends an "[EOF]" and not a "QUIT" as it should be for a
821-Conform system. The problem is, that the Sendmail delivers the Mail
after getting the "." (normal behavior), but Exchange doesn't recognize the
successful delivering, despite the fact Sendmail sends a "250" message. This
"abnormal" disruption of the SMTP-process now happens every time for that
Mail (other Mails were delivered successful while this happens). After
reaching the limit (144 times by default) Exchange sends an NDR to the
original sender.
The "." is not part of the Mail, I checked this, Exchange must send the "."
to signal that the Mail finished.
Maybe it's something inside the Mails.
Any help would be very, very helpfull.
--------------------
- Christian Friebe -
--------------------
"Jim Mackin" <jma...@hastings.edu> wrote in message
news:ek7TGgYpAHA.1840@tkmsftngp03...
>I too am having the same problem. I am also on Exchange 5.5 sp4. This
>phenomenon is happening with increasing regularity. I checked the message
>ID's on the repeated messages. The local ID's that our exchange server
>assigns are different for each message and the ID of the messages that the
>sending server assigns is the same for each.
For the messages that are received multiple times (with the same
Message-ID value and addressed to the same recipient), you might try
contacting the originating site and finding out why they're doing
this.
For messages received in different "batches" I don't think the IMS has
much choice but to create a unique ID for them.
Rich Matheisen [MVP] <rich...@rmcons.com.NOSPAM.COM> wrote in message
news:dpn7atsh2j4ahd24g...@4ax.com...