We have a script sending an SMTP message to our IMS ten times. Each of the ten messages is given its own Exchange message ID (as noted in the tracking logs) and shown to be delivered to the one mailbox that all ten are for. However only one message actually shows up. The unique thing here is that the originator's message ID is the same for all ten messages (intentionally). The tracking logs show ten messages being accepted and even routed to other servers successfully, and even delivered. But I think that since the originator's message ID is the same for all ten messages only the first of the ten is actually delivered. Does store (or the mta) have some sort of SMTP message ID cache to keep track of messages received? Keep in mind that the Exchange message IDs are unique, which means that Exchange is actually looking inside the message to compare host message IDs. And it is not the IMS doing the comparing because the logs show the messages being routed to other servers on its way to the destination server mailbox. We changed the script to modify the original message's host ID and the new one appeared in the Inbox. Hmmmmmm. So by deduction I have concluded that Exchange has some sort of built in message looping/duplication feature to keep what it thinks as the same message from being delivered multiple times because of failed TCP/SMTP connections or something where the receiver things all is well, but the sender doesn't think the message was delivered successfully so it will try again. What do you all think?
Scott. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
