Exchange 2003-Outlook 2003 Missing Recipient Field

I have run across a weird problem running Exchange 2003 and Outlook 2003.

A couple of users have occasionally sent emails to a local recipient(s) (in the same domain) where the recipient field (the TO: field) is blank even though the email is delivered successfully.

Looking at the Sent Items folder the email continues to show no recipient.

I have saved a couple of these emails as a .msg file and looked at them with a text editor and compared them to emails that display properly.

I see the following strangeness.

The X.500 address (legacyExchangeDN) is in the email body 3 times with a mixture of capitalization structures for the recipient.

When the email displays properly the recipient format in the msg file looks like this:


On the emails where the recipient does not display, the recipient format is exclusively upper case (still 3 entries)


In ASDIEDIT the specific legacyExchangeDn is:


When I look at the Exchange Tracking log to see what the server logged as the mail passed though the pattern is largely repeated

One of the emails had 7 recipients, only 2 which showed in the Outlook recipient field, which looked as follows:

;;;;;;Zack Wilbur;Jim Smith

The tracking log recorded the following recipient information:


This last sequence was, as expected, repeated each time for the various tracking codes Microsoft uses to process email. (1027, 1019, 1025, and 1024 for X.500 and 1033, 1036, 1023, and 1028 for SMTP)

The emails are being delivered successfully.  The 2 users I know that occasionally have this issue are remote users at the far end of a VPN connection from the server.  I have yet to see an in-facility user with the issue.

Does anyone know why Microsoft writes the X.500 address 3 times in the email but only one time in the tracking log and why should case sensitivity be an issue?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Satya PathakLead Technical ConsultantCommented:
I would suggest you can go through.
Fred_AlcibiadesAuthor Commented:
Thanks for the suggestion but it seems unrelated to the issue I have.

There is no duplication problem with the legacyExchangeDN and Exchange 5.5 was never a player in the situation.

I have discovered that the Outlook address cache file reflects that same capitalization weirdness, although it is not clear if that is a cause or symptom.  Either way, clearing the cache did not resolve the issue.
Fred_AlcibiadesAuthor Commented:
This turned out to be a conflict between the WAN optimizing software and the firmware on the firewall/VPN endpoint device

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
What was the WAN optimizing software?
What was the firewall/VPN endpoint device want what was the firmware version?
What was the conflict?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.