| Summary: | mapi support for exchange 5.5 in kmail | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Adolf Winterer <adolf.j.winterer> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | colding, jtamate, olivier.lahaye, tuju |
| Priority: | NOR | Keywords: | triaged |
| Version: | 1.5.1 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Adolf Winterer
2003-06-20 14:24:02 UTC
Novel released the Ximian evolution Exchange 2000/2003 connector under GPL! It is available at the following address (May 14 2004): http://www.novell.com/products/connector/ This gives all needed materials to implement the exchange connectivity. Such a feature would help many sysadmins to spread/deploy linux in big companies. Unfortunately, I have no C++ programming skills, but if I can help by testing... Would be awesome feature :-) The real problem for the Ximian connector is that it requires the Enterprise to run the OWA (Outlook Web Access) component of Exchange. Without this (which my company is currently refusing to implement for "security" reasons) the connector doesn't work. Not to mention that it requires you use evolution, which is ok for some... but if you have gotten used to Kmail and like the things that it does switching is a loathsome process. This and ONLY this seems to be the MAJOR barrier to enterprises running other email clients. Joe There are actually two Open source (GPL) libraries out there for using the MAPI protocol other than Ximian Connector. Brutus - Corba library for MAPI access - http://www.omesc.com and SourceXtreme Mapi toolkit - http://www.sourcextreme.com/projects/outlook/mapi/ If I knew more about Kontact I would probably work on implementing these, but I don't and don't have time right now. hope this info helps someone Hi, SourceXtreme is not the answer to your prayers. The SourceXtreme toolkit is "merely" a helper API that wraps complicated parts of native MAPI into simple utility functions. This API is only for native win32 boxes. Brutus, on the other hand, is a platform independent MAPI "proxy" that encupsulated all of extended MAPI into corresponding CORBA methods and types. You can devel a Brutus linux client application and expect it to behave just like a native MAPI win32 client application. This makes Brutus very suitable for linux mail and calendar application like Evolution and KMail. I've created a plugin for Evolution 2.[4,6,8] that makes Evolution connect to Exchange 5.5 and greater using Brutus. It is equally possible for the KMail developers to create a KMail plugin/extension that provides similar functionality. I'm certainly willing to help in any effort to add Brutus (Exchange) functionality into other applications. Just ask and I'll do my best. HTH, jules Any pointers to your plugin? take a look at his website: www.omesc.com and http://www.omesc.com/modules/xoopsfaq/index.php?cat_id=3#q6 You can choose to get the source for the plugin alone or the combined plugin/server source: Plugin source and RPMs: ----------------------- http://www.omesc.com/content/downloads/dist The combined source: -------------------- http://www.omesc.com/content/downloads/brutus-0.9.30.tar.bz2 So cool.... Can't wait for the kmail pluging :-) The Brutus MAPI<->CORBA bridge needs to be run on Windows, right? Is this a problem? Brutus Server is running on some win32 box, yes. It does not have to be any special kind of win32 box, nor should it be. The good thing about this setup is that you never need to touch the Exchange server or anything else that your IT admin might have strong feeling about. Brutus is really the only way to get full MAPI support in a platform independent way. Just for the record, there is another way to get full MAPI support without needing a win32 component like the Brutus Server: use DCE-RPC rather than CORBA, because it's what exchange supports already. Samba-TNG has basic DCE-RPC infrastructure in place, and the guys at http://openchange.org are working on the MAPI interface. This is still a work in progress, much less mature than Brutus. Yes... the joys of on-the-wire reverse engineering versus an API proxy. Any news on a kmail plugin to support MAPI? *** This bug has been marked as a duplicate of bug 78629 *** Bug 78629 is not a duplicate as is states about exchange WEB ACCESS while this bug states about MAPI support. Web Access is not enabled on all companies exchange servers. MAPI for Exchange 2007 is fully documented here: http://msdn.microsoft.com/en-us/library/cc678348.aspx If only I cound code C++ :-( |