Red Hat Bugzilla – Bug 1005072
Unable to authenticate to Exchange MAPI server after update
Last modified: 2014-01-02 05:55:05 EST
Created attachment 794605 [details]
Description of problem:
After update to Evolution 2.32, I'm unable to authenticate to Exchange MAPI server with my existing account.
Creating new MAPI account in Evolution 2.32 works fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create an MAPI account with Evolution 2.28, e.g. in rhel64
2. Update to new Evolution 2.32
Authentication is successful
Interesting, this was supposed to be fixed by , which is included in 0.32.2. I guess there failed something in the (re)create of the profile.
I've a patch ready, there was a problem with profile naming, which changes for 0.32.x. Please note that you still can be asked for a password, these are not part of a backup, but you should not get the error like in your screenshot from comment #0.
Mail and Contacts are working but I'm unable to authenticate to Calendar. It keeps asking for password.
Could you give me your current set, by
$ gconftool-2 --dump /apps/evolution &>evo-gconf.xml
(this can hold your passwords, but can be empty or missing too)
thus I'll be able to try to reproduce it here, please?
All the parts worked fine for me, when I was testing the patch. I suspect the source definition in GConf is somehow broken, references wrong host name, user name or something like that.
Actually this looks like a regression, probably caused by the fix. I'm unable to connect to MAPI Calendar even on clean account in evolution 2.32.
I'll retest with evolution-mapi-0.32.2-6.el6 to be sure.
Confirmed the regression, after update to evolution-mapi-0.32.2-8.el6 cannot authenticate to MAPI Calendar. The password prompt keeps asking for authentication.
Oh, I thought I cover the inconsistency between addressbook and calendar sources, but I obviously did not; I'm sorry for that. I have a fix ready for this.
Updated package evolution-mapi-0.32.2-9.el6 is available now.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.