I've been working on our Exchange 2010 deployment for several weeks now. In initial testing e-mail that had a text/html content type showed a blank body. However, e-mail sent with RTF or Plain Text were fully readable. I've applied Update Rollup 1, and have tried various testing scenarios. Today however, I came across an interesting situation. I logged into the test mailbox using the Outlook Web App and the text/html e-mail was fully readable and properly formatted when Outlook 2007 was closed on the client. I then launched Outlook 2007 on the same mailbox and the message body went blank while I was watching it in my browser. Outlook 2007 seems to be stripping the body of the message if it is text/html while OWA seems happy rendering it and displaying it. Does anybody have any ideas what Outlook 2007 is doing to the message body or is this some strange interaction between Outlook 2007 and Exchange 2010?

If it helps, I installed Outlook 2003 on another computer and opened the mailbox. Outlook 2003 also stripped the body of the message.

More information. Here is the log from Outlook 2007: 2010.01.07 14:51:45 <<<< Logging Started (level is LTF_TRACE) >>>> 2010.01.07 14:51:45 HELPER::Initialize called 2010.01.07 14:51:45 Initializing: Finding a Transport 2010.01.07 14:51:45 MAPI XP Call: XPProviderInit in EMSMDB.DLL, hr = 0x00000000 2010.01.07 14:51:45 MAPI XP Call: TransportLogon, hr = 0x8004011d 2010.01.07 14:51:45 MAPI XP Call: Shutdown, hr = 0x00000000 2010.01.07 14:51:45 MAPI XP Call: XPProviderInit in EMSMDB.DLL, hr = 0x00000000 2010.01.07 14:51:45 MAPI Status: (-- -- ---/--- -- ---) 2010.01.07 14:51:45 MAPI XP Call: TransportLogon, hr = 0x00000000 2010.01.07 14:51:45 Initializing: Found a transport, Error code = 0x00000000 2010.01.07 14:51:45 MAPI XP Call: AddressTypes, hr = 0x00000000, cAddrs = 3, cUids = 1 2010.01.07 14:51:45 MAPI XP Call: RegisterOptions, hr = 0x00000000, cOptions = 2 2010.01.07 14:51:45 MAPI Status: (IN -- ---/OUT -- ---) 2010.01.07 14:51:45 MAPI XP Call: TransportNotify(BEGIN_IN|BEGIN_OUT), hr = 0x00000000 2010.01.07 14:51:45 HELPER::Initialize done, Error code = 0x00000000 2010.01.07 14:51:45 HELPER::GetCapabilities called, Error code = 0x00000000 2010.01.07 14:52:04 HELPER::Uninitialize called 2010.01.07 14:52:04 MAPI Status: (-- -- ---/--- -- ---) 2010.01.07 14:52:04 MAPI XP Call: TransportNotify(END_IN|END_OUT), hr = 0x00000000 2010.01.07 14:52:04 MAPI XP Call: TransportLogoff in EMSMDB.DLL, hr = 0x00000000 2010.01.07 14:52:04 MAPI XP Call: Shutdown, hr = 0x00000000 2010.01.07 14:52:04 Resource manager terminated The Exchange 2010 health check doesn't show any major problems. Still looking.

I know there have been a lot of views on this problem and I isolated and resolved the problem. The problem was the LOCAL anti-virus scanner. I had not installed NOD32 on the servers yet. For some reason on the client side NOD32 (v 4.0.437.0) was wiping out the message body. When I disabled NOD32 then it began working and showing the HTML messages. Many thanks to http://beyondteck.blogspot.com/2006/05/blank-email-messages-in-microsoft.html for pointing me in the right direction.