OK. Thanks all. Is the search base included when searching LDAP from Evo? I can't see it in the debug (my search base is: ou=Users,l=hq,o=NR):
searching server using filter: (|(cn=per*)(sn=per*)) (expecting max 100 results) adding search_op (0x930f890, 24) looked up msgid 24, got op 0x932b160 ldap_search_handler (0x930f890) attr = uamPosixSalt, info = (nil) attr = loginShell, info = (nil) attr = homeDirectory, info = (nil) attr = gecos, info = (nil) attr = gidNumber, info = (nil) attr = uidNumber, info = (nil) attr = sasDefaultLoginSequence, info = (nil) attr = mail, info = 0x80781f8 attr = uid, info = (nil) attr = givenName, info = (nil) attr = fullName, info = (nil) attr = title, info = 0x8078444 value = Research Scientist attr = telephoneNumber, info = 0x8078230 attr = sn, info = 0x80781dc attr = ou, info = 0x807840c value = DART I find this result a bit strange - it can fetch some of the fields (like Research Scientist and DART is from LDAP) but most of the important fields are nil. But the same filter works with ldapsearch: ldapsearch -x -b ou=Users,l=hq,o=NR -h ldap.nr.no "(|(sn=per*)(cn=per*))" This returns a number of records from our ldap (and my record is also there). I had to use simple authentication (-x) with ldapsearch. Does Evolution support this? Any suggestions? Thanks Per Thomas _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
