ptload(): bad response from ptloader server: identifier not found

Jan Kowalsky jankow at datenkollektiv.net
Thu Feb 25 12:25:37 CET 2016


Hi Michel

Am 24.02.2016 um 15:53 schrieb FoxNET Support:
>> Jan, result of the different commands:
>>
>> /usr/lib64/mozldap/ldapsearch -x -h localhost -p 389 -D 'uid=kolab-service,ou=Special Users,dc=foxchange,dc=net' -w "$(grep ^service_bind_pw /etc/kolab/kolab.conf | cut -d ' ' -f3- | head -1)" -b 'cn=kolab,cn=config' '(&(objectClass=*))' aci
>> version: 1
>> dn: cn=kolab,cn=config
>> aci: (targetattr = "*") (version 3.0;acl "Kolab Services";allow (read,compare,
>> search)(userdn = "ldap:///uid=kolab-service,ou=Special Users,dc=foxchange,dc
>> =net");)
>>
>> dn: associateddomain=foxchange.net,cn=kolab,cn=config
>> aci: (targetattr = "*") (version 3.0;acl "Read Access for foxchange.net Users"
>> ;allow (read,compare,search)(userdn = "ldap:///dc=foxchange,dc=net??sub?(obj
>> ectclass=*)");)
>>
>> dn: associateddomain=foxnet.io,cn=kolab,cn=config
>> aci: (targetattr = "*") (version 3.0;acl "Read Access for foxnet.io Users";all
>> ow (read,compare,search)(userdn = "ldap:///dc=foxnet,dc=io??sub?(objectclass
>> =*)");)
>>
>> dn: associateddomain=michelrenard.net,cn=kolab,cn=config
>> [root at spool ~]# /usr/lib64/mozldap/ldapsearch -x -h localhost -p 389 -D 'uid=kolab-service,ou=Special Users,dc=foxchange,dc=net' -w "$(grep ^service_bind_pw /etc/kolab/kolab.conf | cut -d ' ' -f3- | head -1)" -b 'cn=kolab,cn=config' '(&(objectClass=*))' dn
>> version: 1
>> dn: cn=kolab,cn=config
>>
>> dn: associateddomain=foxchange.net,cn=kolab,cn=config
>>
>> dn: associateddomain=foxnet.io,cn=kolab,cn=config
>>
>> dn: associateddomain=michelrenard.net,cn=kolab,cn=config
>>

This looks fine on the first look.
Does the ptloader fails for all your domains? Or only for the secondary
domains and the primary works fine?

If your cyrus-verion supports the ldap lookup in multiple base dns
(which version ?) then I guess a misconfiguration in impad.conf

You can have a look at the ldap access log. Maybe there is a hint what
exactly is the problem during ldap lookup.

I just saw this in the posted logs:

>>>>> Feb 22 19:01:56 spool imaps[29562]: badlogin: localhost.localdomain
>>>>> [127.0.0.1] PLAIN [SASL(-13): authentication failure: bad userid
>>>>> authenticated]

localhost.localdomain. Does your server have a full qualified hostname?

What does hostname -f say?

Regards
Jan


More information about the users mailing list