| Summary: | MAPI support in kmail | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] Akonadi | Reporter: | Antenore <antenore> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | antenore, branislav.klocok, bugs.kde.org, dvratil, erenoglu, kainuja, kdepim-bugs, king_duckz, krah.tm, lomakin.andrey, mail, mail, montel, olivier.lahaye1, peter.kelder, rafael.linux.user, richts, Stephan, stephane.guillou, th0ma7, thomas |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Antenore
2010-02-19 14:54:41 UTC
If we wanna make KDE work, in at this moment MS dominant enterprises, support for mapi is a must. Lacking mapi support id the biggest inhibitor for large enterprise moves to opensource desktop at the moment. Regards, Peter There's a libmapi/libmapi++/OpenChange based Akonadi resource: http://wiki.openchange.org/index.php/Akonadi_Resource So there's probably support for it starting with the KMail which is shipped with KDE SC 4.5. This is a really good news! Thanks a lot! Unlucky I cannot upgrade to 4.5 :-( "So there's probably support for it starting with the KMail which is shipped with KDE SC 4.5." If it's as proto level as Evolution mapi was in 2009 (and still is) when it was included in Ubuntu Karmic, please do not put in official repository! Yes, it is really bad not to have mapi, but it's even worse to make hopeful users to try and disappoint again and again. Changed to product to 'Akonadi'. *** This bug has been confirmed by popular vote. *** (In reply to comment #4) > "So there's probably support for it starting with the KMail which is shipped > with KDE SC 4.5." > > If it's as proto level as Evolution mapi was in 2009 (and still is) when it was > included in Ubuntu Karmic, please do not put in official repository! > Yes, it is really bad not to have mapi, but it's even worse to make hopeful > users to try and disappoint again and again. How much it would cost, in man days, assuring an enough good stability to have it in the official repository? At the moment, which "not official" repositories should I use to test it? Thanks in advance again Antenore Hello Guys, What is the status of this? My company has just migrated to MS Exchange 2007 and they have disabled IMAP. The only way for me to work today is with DavMail, but that is insanely slow. I would be ready to make a financial donation to get this one going. *** Bug 287984 has been marked as a duplicate of this bug. *** Bump for 2013 with linkage to https://bugs.kde.org/show_bug.cgi?id=78629 ;) Evolution did make progress here in contrast to KMail. There an evolution-ews modul, using the Exchange Webservices API (which is good, because it does work with proxies - where the existing mapi connector does only work with direct access to the Exchange Server). https://live.gnome.org/Evolution/EWS This site is not up-to-date because OAB support is already there in 3.6.x.. So maybe this will be a solution for kmail/korganizer/kontact too. Got tired of waiting for this bug to be fixed. I advise everyone to run davmail which acts as a proxy for POP/IMAP/SMTP/Caldav/Carddav/LDAP to exchange. It works and doesn't require a mysql database to be running either. http://davmail.sourceforge.net/ I know this is a free project and all, but shouldn't a 7-8 year old request for a feature be paid attention at a certain point? I need developer which knows it and has a server to test it... There is akonadi-exchange project, which sort of works and Dantti is working on a Qt-based MAPI library and an Akonadi resource. Its already an old request that Kontact (or better Akonadi) should support an Exchange server backend. But the request is still valid! I have already seen a working solution with Evolution. However this is not an option for me. I would like to have it integrated in Kontact. I am not a developer, but an IT Product manager. Is there a way how I can support this? *** Bug 333773 has been marked as a duplicate of this bug. *** +1 :) I gave up long ago on this. The current mechanism to access Exchange server is EWS and it has public API. This is what Evolution uses. I switched to using Evolution due to this. It even has an Activesync backend. We now have a stock EWS resource to support syncing with Exchange servers, I think EWS is much preferred over MAPI theses days. Exchange web service is disabled at my workplace. No problem though as I switched to MacOS X with MS office 2019. Linux is not ready for desktop in professional world and will never be :-/. Good luck. |