8 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] LDAP Address Books in...
FromSent OnAttachments
Stephen MeatheringhamJan 7, 2007 3:48 pm 
Sam VarshavchikJan 7, 2007 4:08 pm 
Stephen MeatheringhamJan 7, 2007 4:19 pm 
Sam VarshavchikJan 7, 2007 6:43 pm 
Stephen MeatheringhamJan 7, 2007 8:19 pm 
Brian CandlerJan 8, 2007 12:36 pm 
Stephen MeatheringhamJan 8, 2007 4:26 pm 
Sam VarshavchikJan 8, 2007 6:41 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [sqwebmail] LDAP Address Books in SQWebMail Web InterfaceActions...
From:Stephen Meatheringham (s.me@adfa.edu.au)
Date:Jan 7, 2007 8:19:16 pm
List:net.sourceforge.lists.courier-sqwebmail

Well, that's not your regular ldapsearch command. This is sqwebmail's code, not OpenLDAP's, and sqwebmail's ldapsearch binary has nothing to do with OpenLDAP's. It is NOT a general purpose LDAP search tool. If it confuses you too much, rename sqwebmail's binary from ldapsearch to foobazblat, and try again.

Yes. I know that, and that is what I said. I did not see any documentation in sqwebmail that obviously told me the format of command line options to the sqwebmail version of ldapsearch.

Generally, if the search fails it does not return anything, which is probably what you're seeing. My guess is that your LDAP search is configured not to accept anonymous binds as searches. LDAP connection negotiation is notoriously difficult to debug. I suggest that you turn up the logging on your LDAP server to the maximum, and run sqwebmail's LDAP search, and see what happens.

No, your guess is wrong. It is configured to accept anonymous binds. I'll look at my Novell eDirectory logs to see if I can determine why it is failing.

Thanks Stephen