Just for your information. I had the same problems with cyrus-imapd-2.2.1 and cyrus-sasl-2.1.14. Specifically I ran cyrus in debug mode and I found that in imapd.c, line 1609, where sasl_getpass() is executed, it returned normally without errors, returning SASL_OK.
After that, when line 1634 was executed, the sasl_getprop(imapd_saslconn, SASL_USERNAME, (const void **) &canon_user) returned the error SASL_NOTDONE ("can't request info until later in exchange"). The problem was magically solved when I upgraded to cyrus-sasl-2.1.15. Regards, Christos Quoting Simon Matter <[EMAIL PROTECTED]>: > >> > >> > >> > >> This error is coming from SASL. Could you please post the relevent > >> contents of imapd.log and auth.log? > > > > Ken, > > > > I have now straced the pid's on 2.1.14 and 2.2.1-BETA. I have also tested > > the 2.2.1-BETA with pwcheck using /etc/sasldb2 and it works well. Looks > to > > me like there is something broken when using saslauthd. FYI, the > > 2.2.1-BETA test is against cyrus-sasl 2.1.10. > > Hmm, I just tested against cyrus-sasl 2.1.15 and it works. Reinstalled > 2.1.10 and it didn't work again. > > Is 2.2.1-BETA supposed not to work with cyrus-sasl 2.1.10? > > > > > Simon -- /** * Christos Soulios * Department of Informatics * University of Athens * e-mail : [EMAIL PROTECTED] */