EV 11 is trashing some plain text emails

[W_Jae_Bishop]

Hi Everyone,

I have yet to see this issue in the forum so here goes.

I am running EV11 (Version: 11.0.0.1351) on Windows Server 2008 R2 64bit and Outlook 2007 SP3 is installed.

EV11 is configured to only archive the messages and not remove them from the exchange server.

My Exchange server is Windows Server 2008 R2 64bit running Exchange 2013 CU6.

Ok, now my issue.

A few users have complained that they have a few blank emails in their inbox.

After exhaustive testing I believe I have narrowed it down to just a certain type of plain text email is getting trashed by EV.

It would seem that if the email header contains

Content-Type: text/plain; format=flowed; charset="iso-8859-1";
 reply-type=original

EV will archive the message properly but it converts the email on the server to a blank HTML email with no content.

There is no content with OWA either.

Users need to restore from the vault to get the message content back.

I am regularly able to reproduce this problem by sending a plain text email with the Windows Live Mail email client through an outside SMTP server to an Exchange user.

When the message arrives it looks fine. Once it gets archived it is no longer a plain text email but rather a blank HTML message.

Any ideas?

Thanks

[TonySterling]

So EV isn't creating shortcuts? 

I think since you can reproduce you should open a call with Support so they can escalate to dev as appropriate.

Best,

[Andrew_G_ · Accepted solution]

I believe this is fixed in Cumulative Hotfix 2. From the release notes:

Plain-text messages could lose their body content after Enterprise Vault archived them from an Exchange 2013 mailbox [3543064]

Any plain-text message that Enterprise Vault archived from an Exchange 2013 mailbox would lose its body content, if you configured the Exchange mailbox policy to do both of the following:

• Keep the original item after archiving instead of deleting it
• Not create a shortcut to the archived item after archiving.

This has been fixed.

[W_Jae_Bishop]

I swear I have been looking for Hotfixes and such but could not find any.

Thanks for the link Andrew. This issue has been resolved.