Duplicate InternalMessageId but the Messages are not duplicates; Messages not received

We migrated about a year ago to a hosted Outlook 2007 environment.  We have an application that sends out informational emails.  Ever since we moved to the hosted email, internal recipients have not received some of these emails.  Months of investigation have revealed that approximately two of every three emails from this application are getting duplicated InternalMessageIds -- the messages have the same time stamp and subject line but different size and body content.

So, how is the InternalMessageId set?  What can we do, either from the application end or in Exchange, to get all the emails delivered?
JLNewmarkAsked:
Who is Participating?
 
mcathcartConnect With a Mentor Commented:
The only way I could find around this issue was to have the subject to be different. Size of email and body made no difference. Only subject.
0
 
mcathcartCommented:
I had this issue on some incoming emails from a customer of ours. Took a long time to track and figure out. What I ended up having to do was have a time stamp put in the subject by the customer on each email coming in and the issue was resolved.
0
 
JLNewmarkAuthor Commented:
Mcathcart, thanks for responding, but I'm not sure I understand.  The two emails would have the exact same time stamp, since the actual header time stamp is identical down to the second.  They are coming from an automated program that is sending them out in batches.  How would putting the time stamp in the subject line change this?  They would still have identical subject lines and different bodies and attachments.
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
mcathcartCommented:
Sorry... I said time stamp, didn't I. I mean they put the load tender number in the subject. Sorry. Each email was for a different load, so that was the best way to identify them.
0
 
JLNewmarkAuthor Commented:
I am checking to see if the subject of these emails can be made different.  They are pre-determined by the type of information being sent, and I'm not sure they can modify the application to do something like, "results #1," "results #2" rather than just "Results" -- to use a very simple example.  

I am hoping that someone has a better idea, and I am wondering, as I said originally, *where* the MessageID is added to the message.  Obviously, the application knows it's sending multiple messages.  Where is this field being populated?  That might help a lot in understanding how we're ending up with messages with the same time stamp and ID.
0
 
JLNewmarkAuthor Commented:
It appears that the MessageID may be set by the AIX SendMail program on the server.  I am working with our AIX Administrator to see if this is correct and if so, if it can be set to force a unique Message ID for a set time period -- even within the same minute would work fine.  If this turns out to be the solution, I will post the details.
0
 
JLNewmarkAuthor Commented:
MessageID is set by the AIX SendMail program but we could not find a way to modify how that was done.

The users have gone back to their application to build in a time-lag for message creation to guarantee unique messageIDs.

My thanks to everyone who tried to help me on this, but I can't see awarding points when there's no real solution.
0
 
JLNewmarkAuthor Commented:
Either this solution or our company's -- increasing the time delay between emails -- is workable.  Neither addresses how the MessageID is set; it does not seem to be a field that can be touched, modified or programmed (i.e., to force unique numbers within the same minute) -- at least, not with our level of knowledge.
0
All Courses

From novice to tech pro — start learning today.