Re: [Evolution] Problems with LDAP to MS Exchange server in Evolution 1.2

[Matt Larson <mlarson verisign com>]

On Wed, 2002-12-11 at 13:21, Chris Toshok wrote:
> You can run wombat in its own terminal (run killev then start wombat
> then run evolution as normal.)  That should produce some debug output
> (specifically the filters used and the ldap search response.)

OK, I got wombat to stay running, but the output isn't particularly
helpful:

  chinook:~ $ wombat
  wombat-Message: Starting wombat
  Wombat up and running
  backend_last_client_gone_cb() called!
  backend_last_client_gone_cb() called!
  wombat-pas-Message: libldap vendor/version: OpenLDAP  2.00.11
  wombat-pas-Message: extensions present:
  wombat-pas-Message: X_OPENLDAP
  wombat-pas-Message: X_OPENLDAP_V2_REFERRALS

  wombat-pas-WARNING **: unhandled value for use_tls, not using it
  wombat-pas-Message: supported server control: 1.2.840.113556.1.4.319
  wombat-pas-Message: supported server control: 1.2.840.113556.1.4.417
  wombat-pas-Message: supported server control: 1.2.840.113556.1.4.529
  searching server using filter: (& (|(cn=Larson*)(sn=Larson*)) )

  wombat-pas-WARNING **: search returned 0

I've verified that my LDAP server does return data for this query, e.g.
this URL works fine in IE:

ldap://<servername>/o=VERISIGN??sub?(&%20(|(cn=Larson*)(sn=Larson*))%20)

That's cutting and pasting the exact query that wombat says evolution
sent (and for which wombat says "search returned 0").  I have configured
my LDAP server in evolution with the same DN (o=VERISIGN) as the URL
above and for a "sub" search, just like the URL.

I'm afraid I still suspect evolution.  Has anyone else made evolution
talk to an MS Exchange LDAP server?

Thanks for any help,

Matt
-- 
Matt Larson <mlarson verisign com>
VeriSign Global Registry Services