Developer Support limitations for public protocols

Original KB number:  2269506

Summary

This article describes how Microsoft Customer Service and Support can help developers about their custom solutions that use various open standards and that integrate with Microsoft Outlook or with Microsoft Exchange.

More information

Microsoft Customer Service and Support don't support custom solutions that use open standards for mail and calendaring, such as vCalendar, Internet iCalendar protocol (iCalendar), Internet Message Access Protocol (IMAP), Post Office Protocol version 3 (POP3), Simple Mail Transfer Protocol (SMTP), and Multipurpose Internet Mail Extensions (MIME).

Exchange and Outlook implement various open standards. But Microsoft provides Developer Support for those standards only when a Microsoft API implements the standard that's being used. For example, Microsoft supports sending SMTP messages by using the System.Net.Mail namespace in Microsoft .NET Framework. But Microsoft doesn't support customers who are trying to interpret an RFC to add an iCalendar body part by using System.Net.Mail.

If you meet problems when you use a third-party API or an open standard, contact the API vendor for support, or refer to the documentation for the open standards. When interoperability problems occur, you should inform the API vendor that to operate successfully with Microsoft products, the API vendor's products must follow the applicable interoperability specifications. If you believe that a Microsoft product isn't following an open specification correctly, Microsoft Customer Service and Support provide support for those scenarios.

For Microsoft documentation for the algorithms that are used to convert iCalendar and vCard to MAPI objects, go to the following websites:

vCard [MS-OXVCARD]

iCalendar [MS-OXCICAL]

For information about support for Microsoft Open Protocol specifications, go to the following websites:

Microsoft Exchange Server and Outlook Standards

User forums and blogs