GNOME Bugzilla – Bug 237383
Ximian Evolution 1.2.1 Red Hat 8.0 Build LDAPS Problems
Last modified: 2013-09-10 14:04:09 UTC
First the error: I'm working on setting up an ldap server on a stock Red Hat 8.0 system and have it running with ldap. I now want to swtich to ldaps but the slapd server reports the following error when Evo 1.2.1 tries to connect: connection_get(10) connection_get(10): got connid=1 connection_read(10): checking for input on id=1 TLS trace: SSL_accept:before/accept initialization TLS trace: SSL_accept:error in SSLv2/v3 read client hello A TLS: can't accept. TLS: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol s23_srvr.c:565 connection_read(10): TLS accept error error=-1 id=1, closing connection_closing: readying conn=1 sd=10 for close connection_close: conn=1 sd=10 Connecting with openssl s_client -state -debug -connect server:ldaps seems to work fine. The ldap server reports the connection so it doesn't appear to be the server. Then the discovery: I've got it working fine with Evolution 1.2.1 using Red Hat's build under the Phoebe beta. Using the Ximian Red Carpet build under Red Hat 8.0, it doesn't work at all. Plain ldap works fine but ldaps does not. Both cases are talking to the same 2.0.25 slapd running on a Red Hat 8.0 server. So it looks like this could be a build specific problem.
Another somewhat related bug is that after setting the default contacts folder to an LDAP directory, adding contacts by right-clicking on an email address in the preview pane fails to add the address to any contact database, local or LDAP. This occurs when using the Ximian build under Red Hat 8.0. Trying the same operation under the Red Hat build of Evolution under the 8.1 beta, it works perfectly. Any hope of getting these two apparent build bugs fixed any time soon?
The 1.2.2 update doesn't fix the problem. I've verified that it exists with a completely new account trying to connect to the ldaps server.
The right-clicking bug (Contact Quick-Add) is not really a bug in the way I originally thought it was. It works fine for "Joe User <joe@joe.com>" but fails silently for "Joe <joe@joe.com>", probably due to how the LDAP server needs firstname lastname in the cn? After having it fail, if I try again and add anything to the fullname field so it has two words, it adds it fine. So it's only a bug in that it should probably tell you that the add failed.
Adding dobey to the Cc: list of what may be a build issue.
the ldap add failure is because the ldap "person" objectclass (which we use) requires a sn (surname) field to have a value.
... and appears to silently fail because Evo doesn't report the LDAP error back to the user...
The second issue user mentioned is resolved. Evolution 1.2.1 and Red Hat 8.0, no way to check the issue. Closing this as OBSOLETE.