GNOME Bugzilla – Bug 579185
Can't setup SSL connection
Last modified: 2010-05-31 17:36:44 UTC
Please describe the problem: MAPI authentication failed. Status in “evolution-mapi” source package in Ubuntu: New Bug description: Binary package hint: evolution error message is: MapiLogonProvider:MAPI_E_NETWORK_ERROR Exchange server requires secure connection via SSL,but there is no option to set SSL. From looking at other info on web,it appears that this does not occur if SSL is not required on the server. Get similar problem using imap on first setup server connection is not set to SSL, but I can then go into preferences set SSL and then it works, but I can't get past the setup wizzard with MAPI, so can't get to the server preferences for the exchange server. The exchange server name, domain name and user name are all correct. How can I set SSL ? Computer is eeepc 900 running Ubuntu 9.04 beta Evolution is 2.26.0 with Exchange MAPI added via Synaptic Package Manager ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/evolution Package: evolution 2.26.0-0ubuntu2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution Uname: Linux 2.6.28-11-generic i686 Steps to reproduce: 1. Use Evolution to try to set up to connect to an Exchange Server that requires an SSL connection to the server. Will not Authenticate 2. 3. Actual results: MapiLogonProvider:MAPI_E_NETWORK_ERROR Expected results: I would expect the server to Authenticate Does this happen every time? Yes Other information: Most info on the web suggests this Authentication problem does not occur on an server in which SSL connection is not required.
*** Bug 579186 has been marked as a duplicate of this bug. ***
*** Bug 579001 has been marked as a duplicate of this bug. ***
*** Bug 581059 has been marked as a duplicate of this bug. ***
This may appear to the original reporter as a NORMAL MAJOR bug; however, due to an impending enterprise upgrade to MAPI with mandatory SSL, this has now become an IMMEDIATE MAJOR fix. Evolution is a good tool, but without the SSL support, we will be forced to find another email client with SSL capabilities for MAPI. How do we get the priority bumped up, or get the evolution team to understand that MAPI with SSL is not the "rare occurrence" they believe it is?
The same problem holds for me. As I use the calendar functionality of Exchange intensively I currently cannot switch to evolution as long as the SSL support is lacking.
This is a major block to using the software for a large number of users. It needs to be moved to urgent!!
As per the information i got Fix is more on samba side then libmapi will just use a flag to use SSL or not.. which evolution will toggle
Same here. I have to connect to an ssl only enabled exhange server. Before the admins had the bright idea to move to ssl I could connect to the server using exhnage-mapi.
libmapi 0.9 would fix this issue. http://mailman.openchange.org/pipermail/devel/2009-December/001431.html
Bug 593387 should be marked a duplicate of this bug.
I can confirm that libmapi 0.9 fixes this issue for me.
Created attachment 162141 [details] [review] proposed ema patch for evolution-mapi; This adds "Use secure connection" check box in the account preferences, and when it is checked then there is stored in the MAPI profile that it should use SSL over RPC, which seems to be necessary for (some?) Exchange 2010 servers. If you can, give it a try, please, and let me know. Just note that one needs to re-authenticate, to take changes in the effect, and maybe also disable and enable the account, to have this propagated to calendar/address book as well. Thanks in advance. Disclaimer: The patch is based on the work and investigation of Andrew Jones [1] [1] http://www.jones.ec/blogs/a/
I got a confirmation from Andrew on IRC that it works for him, thus I'm committing this to master. I cannot to stable because string addition and a UI change, where both shouldn't be done on stable release. Note that change in "Use SSL connection" requires re-authentication to let it work, otherwise old state is still used. Created commit 22d81d4 in ema master (0.31.3+)