Making Microsoft MAPI not work with GroupWise
Date: April 1997
To: Bill Mangum’
Date: 4/9/97 11:14AM
Subject: RE: Thank you for being persistent on the product delivery
: Sorry that it took so long to get back to you. I guess it’s better late then never (although that is a horrible excuse). In any case, here are some answers to your questions.
: The truth is that contrary to some published reports, MAPI has not changed in quite some time. What has changed with Outlook is the extent to which we rely on MAPI. Outlook ’97 is heavily MAPI dependent and that is the reason most MAPI service providers that were previously written for exchange no longer work with Outlook. Over the past few months I have been working with several other developers that have run into similar problems and it has all come down to beefing up their MAPI service providers.
: In order for GroupWise to work as the primary store with Outlook, there are a few requirements of the store itself. The most important one is that the store need to support named properties and the ability to create named properties on MAPI items on the fly. This is a piece of functionality that is heavily used by Outlook.
: I will forward you some information that I have put together for other developers and I hope that they come in handy in your work to update your MAPI drivers to support Outlook.
: If you have any questions, please feel free to contact me.
David Raissipour Outlook Product Planner Microsoft Corporation Mailto:DavidRai@Microsoft.com
On Friday, December 20, 1996 11:33 AM, Bill Mangum [SMTP:BMANGUM@novelI.com] wrote: : > David
: > I did receive the product and there have been a couple of programmers reviewing the compatibility of Outlook with GroupWise. As you may suspect because of the changes in the version of MAPI that you have used with Outlook and probably Exchange 5 back-end also the. compatibility has fallen between our products.
: > You had mentioned that you had work under way to do some write up of the changes and issues with the new version of MAPI that you are using. Also the specific calls that Outlook is making against a MAPI store, MAPI Address books, and the MAPI MTA. I would like to make sure that we are on the list of developers to receive that doc as soon as you are ready to have someone look at it for testing purposes.
: > Also if you can give us any insight as to how the MAPI "standard" changes are evolving and what to expect in the next several months (year) that would be great.
: > Thank you again
Bill Mangum Novell GroupWise Division Product Manager- Admin/Dir/Mngmt bmangum@novell.com NWA 000201
Synopsis
Snippet
From: David Raissipour: Sorry that it took so long to get back to you. I guess it’s better late then never (although that is a horrible excuse). In any case, here are some answers to your questions.
: The truth is that contrary to some published reports, MAPI has not changed in quite some time. What has changed with Outlook is the extent to which we rely on MAPI. Outlook ’97 is heavily MAPI dependent and that is the reason most MAPI service providers that were previously written for exchange no longer work with Outlook. Over the past few months I have been working with several other developers that have run into similar problems and it has all come down to beefing up their MAPI service providers.
: In order for GroupWise to work as the primary store with Outlook, there are a few requirements of the store itself. The most important one is that the store need to support named properties and the ability to create named properties on MAPI items on the fly. This is a piece of functionality that is heavily used by Outlook.
: I will forward you some information that I have put together for other developers and I hope that they come in handy in your work to update your MAPI drivers to support Outlook.
: If you have any questions, please feel free to contact me.
David Raissipour Outlook Product Planner Microsoft Corporation Mailto:DavidRai@Microsoft.com
On Friday, December 20, 1996 11:33 AM, Bill Mangum [SMTP:BMANGUM@novelI.com] wrote: : > David
: > I did receive the product and there have been a couple of programmers reviewing the compatibility of Outlook with GroupWise. As you may suspect because of the changes in the version of MAPI that you have used with Outlook and probably Exchange 5 back-end also the. compatibility has fallen between our products.
: > You had mentioned that you had work under way to do some write up of the changes and issues with the new version of MAPI that you are using. Also the specific calls that Outlook is making against a MAPI store, MAPI Address books, and the MAPI MTA. I would like to make sure that we are on the list of developers to receive that doc as soon as you are ready to have someone look at it for testing purposes.
: > Also if you can give us any insight as to how the MAPI "standard" changes are evolving and what to expect in the next several months (year) that would be great.
: > Thank you again
Bill Mangum Novell GroupWise Division Product Manager- Admin/Dir/Mngmt bmangum@novell.com NWA 000201