On Thu, 2004-10-14 at 08:14, Eric Lambart wrote:
On Thu, 2004-10-14 at 08:03 -0700, Thomas Spuhler wrote:On Thu, 2004-10-14 at 07:30, Per Thomas Jahr wrote:Hi, I'm having some problems with getting Evolution 2.0.1 to work together with the company LDAP. Is there someway I can get a log file or some more info from Evolution when it communicates with the LDAP server? There is no error messages from Evolution but I can't get any results when I search the LDAP either... ThanksYou are not the only one and I never got a reply to this question on this list. Evo does not connect (at least I don't know how) to the kolab server, whereas Netscape/Mozilla or Kmail does not have this problem. It seems that Evo finds the LDAP server, but it does not accept the password. It keeps on asking for the password.Well, I am only *just* starting to figure out how to set up LDAP on my mail server, and was messing around with it last night. I can't help you with the overall issues, but as far as logging go, if you shut down Evo by running: $ evolution --force-shutdown and then $ /usr/libexec/evolution-data-server-1.0 (for RedHat 9; if it's not in that directory, try this to find it): $ locate -r "evolution-data-server-1.0$" After you've got EDS started, you can just start Evolution normally, and you'll see LDAP-related messages appear in the terminal window where EDS is running. But unfortunately, from my limited experience, authentication problems don't seem to give any feedback at all. I just wish someone had written a simple document for "how to set up OpenLDAP from scratch to store your Evolution contacts and share them with other clients."
Kolab sets them up very nicely if you use Mandrake. Entering the contacts is WEB browser based and everybody can use them. It's a company (or home) directory. Kmail and Mozilla take advantage of it nicely. Just start the name in an e-mail and it will have autocompletion (similar as when the name is already in the Evo address book). Evo probably will do the same. The only problem is how to connect Evo to it. You are right. A documentation would help.
I guess I may have to be the one who does it. Good luck! Eric
Tom
Attachment:
signature.asc
Description: This is a digitally signed message part