saslauthd+ldap is very reliable for me. I had this one issue which seem ed to occur when I restarted OpenLDAP, but I think that's been fixed in CVS.
Maybe you should upgrade LDAP to 2.1.x series?
Try running ethereal and listening to the ldap traffic when the bad logins occur. Or running OpenLDAP with extra logging.
--Kervin
Felix Cuello wrote:
Hello! I'm actually working with Cyrus 2.1.9 and sasl2.1.9 and sometimes (solved the entrophy problem) my POP server sometimes returns incrrect username or password. It could be because I'm using ldap beta support of saslauthd?. I'm working with LDAP 2.0.23.Thanks a lot! Felix
