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:Brian Candler (B.Ca@pobox.com)
Date:Jan 8, 2007 12:36:44 pm
List:net.sourceforge.lists.courier-sqwebmail

On Mon, Jan 08, 2007 at 03:19:39PM +1100, Stephen Meatheringham wrote:

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.

tcpdump -i eth0 -n -s0 -X tcp port 389

may give some clues - run this in one window while running the sqwebmail ldapsearch command in another.

The LDAP protocol is a packed binary representation (using ASN.1), but at least you should see (a) that it connects, (b) that it connects to the correct host, and (c) you may see whether it gets past the 'bind' stage and as far as sending the search.

A possible problem is if there's an LDAPv2 bind going to an LDAPv3 server, or vice versa. This can be determined from the full tcpdump output, with a bit of work, although getting it from the server logs would be easier.

Regards,

Brian.