Forgive me belaboring the point, I'm obtuse sometimes. Would you mind sending a snippet of the tracking log that shows one of your tests?
======================================================= Andy Webb [EMAIL PROTECTED] www.swinc.com Simpler-Webb, Inc. Austin, TX 512-322-0071 -- Way to go USPS Cycling Team and Lance Armstrong!! -- ======================================================= -----Original Message----- From: Bueffel, Scott M - CNF [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 14, 2001 12:15 PM To: Exchange Discussions Subject: RE: Issue with IMS and multiple messages Yes, the tracking log shows the messages actually being delivered to the mailbox successfully each time, even though only the first one actually shows up. We stripped the host's message ID and sent it five times and all five came in successfully. So our suppositions were correct. Thanks for your help. Scott. -----Original Message----- From: Webb, Andy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 14, 2001 8:33 AM To: Exchange Discussions Subject: RE: Issue with IMS and multiple messages Does it show it was delivered? What is the full set of events in the tracking log for that message ID? ======================================================= Andy Webb [EMAIL PROTECTED] www.swinc.com Simpler-Webb, Inc. Austin, TX 512-322-0071 -- Way to go USPS Cycling Team and Lance Armstrong!! -- ======================================================= -----Original Message----- From: Bueffel, Scott M - CNF [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 14, 2001 9:58 AM To: Exchange Discussions Subject: RE: Issue with IMS and multiple messages Our SMTP virus scanner strips out .exe's but delivers the message. Sometimes the recipient needs actually needs the .exe so requests it. The script takes the original message with the attachment and resends it through the scanner to scan the .exe and send it on. But since this is the same as the first message (only with the attachment) the host's message ID is the same, so the message would not be delivered. The UNIX group running the SMTP server said they think they can have script modify the original message ID so that it would be sent (when they did it manually the message came fine). The question was if there was a need for that, so we wanted to find out if the message ID was the reason the multiple copies were not delivered. The thing I don't like about it is the tracking logs show those multiple message actually being delivered. Although instances like this are rare, it can really mess up your message tracking if a log says it was delivered when it really wasn't. Thanks, Andy. Scott. -----Original Message----- From: Webb, Andy [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 13, 2001 11:17 PM To: Exchange Discussions Subject: RE: Issue with IMS and multiple messages Yes, Exchange does try to prevent a user receiving multiple copies of the same message. Take for example a user who is on two separate distribution lists which are included in the address fields of a message. Depending on where those DLs are expanded, there may be two messages routed to the user. This is picked up by tracking the sender message Id and filtered. Why is your script generating a messageID? Why not just leave that header out and let the receiving system supply a unique ID. ======================================================= Andy Webb [EMAIL PROTECTED] www.swinc.com Simpler-Webb, Inc. Austin, TX 512-322-0071 -- Way to go USPS Cycling Team and Lance Armstrong!! -- ======================================================= -----Original Message----- From: Bueffel, Scott M - CNF [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 13, 2001 6:10 PM To: Exchange Discussions Subject: Issue with IMS and multiple messages 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] _________________________________________________________________ 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] _________________________________________________________________ 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] _________________________________________________________________ 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] _________________________________________________________________ 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] _________________________________________________________________ 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]
