An IMAP user has sent a command that the information store does not process correctly. The following command may cause this issue:
007H FETCH 1 (INTERNALDATE RFC822.SIZE FLAGS ENVELOPE BODY UID)
NOTE: The 007H and the 1 following the FETCH command may be different depending on conversation key and the message being accessed.
You can configure the IMAP protocol in the Exchange Server Administrator program to allow Rich Text Format (RTF). This setting enables the IMAP protocol to encode any OLE-embedded objects into a TNEF stream. When the preceding command is given to the IMAP service to retrieve a message with an embedded OLE object, such as a Clip Art picture, the preceding command may cause the store to crash. When the preceding command cannot correctly encode the OLE object into a TNEF stream. The preceding command works correctly when the setting to allow RTF is not set in the Administrator program.
To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
191914 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
The following files are available for download from the MicrosoftDownload Center:
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
You can turn off the option to allow RTF in the Administrator program. To do so:
Start the Administrator program, and connect to the server that is experiencing this issue.
Locate the Site\Configuration\Protocols object.
Double-click the IMAP4 object in the right pane.
Click the Message Format tab.
Click to clear the Use Microsoft Exchange rich-text format check box.
Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.