Re: Cyrus IMAP 2.2.3 & ldapdb auxprop

2004-03-05 Thread Igor Brezac
On Fri, 5 Mar 2004, Alex Deiter wrote: > Igor Brezac пишет: > > >>If ldapdb auxprop plugin contacts with remote ldap server (i.e. > >>sasl_ldapdb_mech: EXTERNAL is not possible): > >> > >> > >Why not? > > > > > How will ldapdb contact with removed ldap the server using EXTERNAL? > Use TLS ? I d

Re: Cyrus IMAP 2.2.3 & ldapdb auxprop

2004-03-05 Thread Igor Brezac
Does sasl CVS version work? This may be a gssapi sasl issue. -Igor On Fri, 5 Mar 2004, Alex Deiter wrote: > Igor Brezac пишет: > > But cyrus-imap 2.1.16 works fine for me with same configurion as > cyrus-imap 2.2.3: > > >>sasl_pwcheck_method: auxprop > >>sasl_auxprop_plugin: ldapdb > >>sasl_ld

Re: Cyrus IMAP 2.2.3 & ldapdb auxprop

2004-03-04 Thread Alex Deiter
Igor Brezac пишет: But cyrus-imap 2.1.16 works fine for me with same configurion as cyrus-imap 2.2.3: sasl_pwcheck_method: auxprop sasl_auxprop_plugin: ldapdb sasl_ldapdb_uri: ldap://server.komi.mts.ru sasl_ldapdb_mech: GSSAPI # cyradm --user test --auth CRAM-MD5 solveig Password: solveig.k

Re: Cyrus IMAP 2.2.3 & ldapdb auxprop

2004-03-04 Thread Alex Deiter
Igor Brezac пишет: If ldapdb auxprop plugin contacts with remote ldap server (i.e. sasl_ldapdb_mech: EXTERNAL is not possible): Why not? How will ldapdb contact with removed ldap the server using EXTERNAL? Use TLS ? Can you use GSSAPI mech with ldapsearch? Yes: # kinit -k -t /etc/kr

Re: Cyrus IMAP 2.2.3 & ldapdb auxprop

2004-03-04 Thread Igor Brezac
On Fri, 5 Mar 2004, Alex Deiter wrote: > If ldapdb auxprop plugin contacts with remote ldap server (i.e. > sasl_ldapdb_mech: EXTERNAL is not possible): Why not? > sasl_pwcheck_method: auxprop > sasl_auxprop_plugin: ldapdb > sasl_ldapdb_uri: ldap://server.komi.mts.ru > sasl_ldapdb_mech: GSSAPI

Re: Cyrus IMAP 2.2.3 & ldapdb auxprop

2004-03-04 Thread Alex Deiter
If ldapdb auxprop plugin contacts with remote ldap server (i.e. sasl_ldapdb_mech: EXTERNAL is not possible): sasl_pwcheck_method: auxprop sasl_auxprop_plugin: ldapdb sasl_ldapdb_uri: ldap://server.komi.mts.ru sasl_ldapdb_mech: GSSAPI i got error: slapd[5483]: do_sasl_bind: dn () mech GSSAPI sl

Re: Cyrus IMAP 2.2.3 & ldapdb auxprop

2004-03-03 Thread Alex Deiter
Igor Brezac wrote: 2.2 CVS HEAD (A little newer than 2.2.3)... If liblber.so.202 comes from openldap 2.2.6 you should be good to go. After rebuild & reinstall cyrus-sasl-2.1.17, openldap-2.2.6, ldapdb (from contrib openldap-2.2.6) and cyrus-imap-2.2.3 it works fine for me: # /usr/local/bin/im

Re: Cyrus IMAP 2.2.3 & ldapdb auxprop

2004-03-02 Thread Alex Deiter
> Well, this is a bug in cyrus and openldap libs (and the sasl lib which > prevents cyrus from being fixed). Fortunately, > http://www.openldap.org/its/index.cgi?findid=2926 fixes the problem. > Although, the fix is available in openldap 2.2.6 and 2.1.27. Yes, therefore I have updated OpenLDAP up

Re: Cyrus IMAP 2.2.3 & ldapdb auxprop

2004-03-02 Thread Igor Brezac
On Tue, 2 Mar 2004, Alex Deiter wrote: > > Well, this is a bug in cyrus and openldap libs (and the sasl lib which > > prevents cyrus from being fixed). Fortunately, > > http://www.openldap.org/its/index.cgi?findid=2926 fixes the problem. > > Although, the fix is available in openldap 2.2.6 and 2

Re: Cyrus IMAP 2.2.3 & ldapdb auxprop

2004-03-02 Thread Igor Brezac
On Tue, 2 Mar 2004, Alex Deiter wrote: > hi, > > After upgrade Cyrus IMAP from 2.1.16 up to 2.2.3 following setup does > not work: > mail client -> Cyrus IMAP -> Cyrus SASL -> ldapdb auxprop -> OpenLDAP > > cyrus log: > pop3[32386]: bad userid authenticated > pop3[32386]: badlogin: server.komi.mt

Cyrus IMAP 2.2.3 & ldapdb auxprop

2004-03-02 Thread Alex Deiter
hi, After upgrade Cyrus IMAP from 2.1.16 up to 2.2.3 following setup does not work: mail client -> Cyrus IMAP -> Cyrus SASL -> ldapdb auxprop -> OpenLDAP cyrus log: pop3[32386]: bad userid authenticated pop3[32386]: badlogin: server.komi.mts.ru[1.1.1.1] plaintext bill SASL(-13): user not found: