XADM: CDO.Message Object that Contains Unicode Is Not Correctly Identified

When you programmatically load a Unicode text file into a CDO.Message object, and then you check the ContentMediaType property of the message object, the text/plain type is returned instead of themultipart/signed type.

If you convert the document to ANSI, it is correctly recognized as multipart/signed.

This problem occurs because Microsoft Collaboration Data Objects for Windows 2000 (CDOSYS) does not parse the MIME message headers correctly when the message is loaded from a Unicode stream. This occurs because CDOSYS and Microsoft Collaboration Data Objects for Exchange 2000 Server (CDOEX) use the MimeOLE functionality to parse the message headers and body parts of messages. This functionality is provided by Microsoft Outlook Express in Inetcomm.dll and was not designed to support Unicode streams.

To work around this problem, configure your program to use ANSI instead of Unicode text streams.

This is a design limitation in Outlook Express.