Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 794605[details]
Screenshot
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):
evolution-2.32.3-23.el6
evolution-mapi-0.32.2-6.el6
openchange-1.0-4.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Create an MAPI account with Evolution 2.28, e.g. in rhel64
2. Update to new Evolution 2.32
Actual results:
Cannot authenticate
Expected results:
Authentication is successful
Additional info:
Interesting, this was supposed to be fixed by [1], which is included in 0.32.2. I guess there failed something in the (re)create of the profile.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=631621
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.
Could you give me your current set, by
$ gconftool-2 --dump /apps/evolution &>evo-gconf.xml
and your
~/.local/share/evolution/mapi-profiles.ldb
~/.gnome2_private/Evolution
(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.
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.
http://rhn.redhat.com/errata/RHSA-2013-1540.html
Created attachment 794605 [details] Screenshot 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): evolution-2.32.3-23.el6 evolution-mapi-0.32.2-6.el6 openchange-1.0-4.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create an MAPI account with Evolution 2.28, e.g. in rhel64 2. Update to new Evolution 2.32 Actual results: Cannot authenticate Expected results: Authentication is successful Additional info: