Exchange 2010 Outlook Clients receive blank emails

After recently migrating from Exchange 2003 to Exchange 2010, users have begun to receive random emails that have blank message bodies but the subjects and other data is intact. (We are currently in coexistence but all mailboxes are on 2010 and mail routes correctly, etc)

OWA displays these messages without issue. Outlook clients range from 2003-2007, I am still trying to see if it occurs only in 2003. Encrypted communications on Exchange has been disabled for the 2003 clients to work (plan to re-enable it client and server side at a later date).

There is no AV filtering on the clients for email, and the blank email is received locally within the organization as well as from outbound sources.

Is it possible a certificate problem could cause this? Again, OWA seems to display the messages fine.
SupA1Asked:
Who is Participating?

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

x
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.

Glen KnightCommented:
And there is no Antivirus software on the client machines?
I have seen AV software cause this but if you don't have any then that rules that out.
0
SupA1Author Commented:
Yes, there is no AV client software that filters email right now. I have verified this only occurs on Outlook 2003 clients, 2007 is fine.
0
Glen KnightCommented:
I am not worried about the filtering of email.
Do you have ANY virus software in the clients at all? Even if email scanning has been disabled cn you uninstall it?

Also try to run the outlook detect and repair from the help menu in outlook.
0
SupA1Author Commented:
After disabling the AV client the same thing happened, outlook detect and repair did not work. What did seem to fix the issue is turning on cached exchange mode... though I have no idea why this would be required.
0

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
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
Exchange

From novice to tech pro — start learning today.