XCON: Incoming Messages from HP OpenMail Include Winmail.dat

 Last reviewed: February 12, 1998
Article ID: Q169670
The information in this article applies to:
  • Microsoft Exchange Server, version 4.0 and 5.0

SYMPTOMS

Attachments on incoming messages from a Hewlett-Packard (HP) OpenMail X.400 connector may include a Winmail.dat attachment if the Microsoft Exchange Server Message Transfer Agent (MTA) is build 995.17 or higher. HP OpenMail can use Microsoft Mail clients with an HP MAPI driver.

CAUSE

The remote system may be sending the Winmail.dat as an FTBP of type mapiAttachment. This is the same value being used for attached files. Normally, the Winmail.dat file is tagged as type TNEF. When the MTA sees the mapiAttachment tag, it assumes it is just another bodypart, and handles it accordingly. If the bodypart was tagged as type TNEF, the MTA would parse it out and use the details inside.

MapiAttachment uses the OID 0x2a864886f714030a02

TNEF uses the OID 0x2a864886f714030a01

The OID can be seen in the ASN.1 parsed data in the attribute P2_RegisteredIdentifier. Microsoft provides an ASN.1 parser in the BackOffice Resource Kit called Aspirin.

WORKAROUND

Configure the HP OpenMail MAPI driver to not generate a Winmail.dat file on outgoing messages. This is done in the Msmail.ini file, in the following section: 

   [OpenDesk Transport]
   EncodeAttachInfo=1
If EncodeAttachInfo is "0", the Winmail.dat file will not be generated. If it is a "1", the Winmail.dat file will be generated.

If the workaround is impractical to implement, see the status section for a possible resolution.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server, version 4.0. A supported fix is now available but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. The fix for these symptoms will also resolve any attachment issues you may be experiencing with incoming MAPI0 Winmail.dat files. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

Keywords          : kbbug4.00 kbbug5.00 kbfix5.00.sp2 XCON kb3rdparty buglist4.00
Version           : WinNT4.0,5.0
Platform          : winnt
Issue type        : kbbug
Solution Type     : kbfix

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.