Red Hat Bugzilla – Bug 166627
Evolution does not connect to exchange server correctly using x86_64 version
Last modified: 2007-11-30 17:07:19 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.10) Gecko/20050719 Red Hat/1.0.6-1.4.1 Firefox/1.0.6
Description of problem:
Using Evolution to connect to an exchange server simply will not work ;-)
I have two (virtually) identical installs of RHEL4-WS update 1. One is an i386 install an Evolution connects to exchange beautifully. One is an x86_64 install and Evolution fails to authenticate when connecting to the exchange server.
Version-Release number of selected component (if applicable):
evolution-2.0.2-16.x64_64.rpm, evolution-connector-2.0.2-5.x86_64.rpm, evolution-data-server-1.0.2-7.x86_64.rpm
Steps to Reproduce:
1. Install RHEL4-WS on an x86_64 platform
2. Attempt to connect to an exchange server
Actual Results: A "could not authenticate to server. (Passowrd incorrect?)" error dialog appeared.
Expected Results: I should have had access to exchange...
I flagged this as high because it is a showstopper for my migration to RHEL4. I noticed that the evolution owner likes debug output, so I ran the debug steps requested in other emails and will attach the output.
Created attachment 118033 [details]
Debugging output from evolution and exchange storage component
Thanks for this report, and for the debug output you attached.
What versions of libsoup are installed (on both machines)?
Are the evolution accounts on both machines configured in exactly the same way?
The settings are stored in GConf, so if the home directory is shared between
machines they will be. Otherwise, please ensure that the x86_64 machine's
configuration matches that of the working i386 machine.
It may help if you could run this command:
"gconftool-2 --dump /apps/evolution/mail > mail-settings.xml" on both machines
and attach the results to this bug (named appropriately). Note that these will
contain your account settings and would be visible in bugzilla.
In addition, please can you follow the same steps you used for x86_64 to
generate debug output for the working i386 box; this will help in tracking down
the details of the Exchange setup. You may want to review the output and
truncate it, since after correctly authenticating it may contain your data (such
as the names of your mail folders).
Even better would be a full "tcpdump -s0" of all traffic during authentication
between client and server, taken on both the working and non-working clients,
though you may wish to provide this independently of bugzilla, since it will
probably contain security-sensitive data.
Don't ask for much, do ya? ;-)
Yes, the configs are identical. Or, at least, they are identical for practical
purposes. I can't possibly send you relevant parts of the mail-settings or the
tcpdump. Security would kill me. I am emailing the relevant debug output from
the working box (from a different email address than on my bugzilla account). I
trimmed it right after the login exchange.
libsoup-2.2.1-1 on both. These are identical installs - I did one yesterday and
one today and have run the same updates against them.
Of course, the x86_64 box has both the x86_64 and i386 libsoup installed.
So, out of curiosity, is there any sane way to go up to evolution-2.2 and
associated on a RHEL4 box to try it out? I'm kind of willing to re-install the
box afterward if necessary. That is, if that is a path that might get me to a
working condition sooner ;-)
Thanks for your feedback. It looks like you're running into a 64-bit
cleanliness bug in the NTLM authentication code that was tracked by upstream here:
It appears to still affect the RHEL-4 libsoup and evolution-connector packages.
I'll roll you some test packages containing the fixes for that bug, since
comment #4 suggests to me that you'd consider trying them; they would be for
Evolution 2.0, rather than 2.2. (They won't be "officially supported" at this
I've built test packages for x86_64 RHEL4 with the fixes for that bug and
uploaded them here:
Please install both packages. Do they fix the authentication problem you've
Just installed them and the authentication issue seems to be fixed. Thanks!
Since this was the only thing standing between me and a workstation with dual
24" flat panel displays, you can imagine how happy I am to get the fix ;-)
Excellent - thanks for the feedback.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
I am still seeing issues authenticating to our Exchange server's using IMAP
over SSL and NTLM/SPA.
I upgraded the libsoup libraries as suggested by the errata and i see proper
authentication only 1 out of 10 tries i attempt to provide my password(Earlier
it just kept failing).
POP does not work at all with SSL and NTLM
The above works if i select "plain password" as authentication mechanism.
Following is the list of installed RPM's for evolution and libsoup.
evolution-connector 2.0.2 5 x86_64
evolution-devel 2.0.2 16 x86_64
evolution-data-server-devel 1.0.2 7 x86_64
libsoup 2.2.1 4 x86_64
evolution-webcal 1.0.10 1 x86_64
evolution 2.0.2 16 x86_64
libsoup-devel 2.2.1 4 x86_64
libsoup 2.2.1 4 i386
evolution-data-server 1.0.2 7 x86_64
evolution-data-server 1.0.2 7 i386
mkapoor: Thanks for adding this information.
We discovered another 64-bit issue with the connector in bug 175640, which was
fixed in http://rhn.redhat.com/errata/RHBA-2006-0483.html with
You may want to try upgrading to this version and see if it helps. If you still
run into problems, please contact Red Hat Support and we'll take things onwards
from there. See https://www.redhat.com/apps/support/
I hope this helps.
Yes, i have even tried upgrading to all evolution and libsoup packages made
available from RHEL4 Update 4. Doing so also does not resolve the issue.
I am also seeing this on RHEL3 Update 7 running on x86_64
I opened a NEW bug (205362) for this issue.