> Carsten Hoeger wrote: > >>What about this issue: >> >>http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&searchterm=request%20info%20until%20later&msg=23996 >> >>Using 2.2.3 and saslauthd I get the same error. >> >>Process 19491 attached - interrupt to quit >>select(1, [0], NULL, NULL, {1480, 440000}) = 1 (in [0], left {1477, >> 980000}) >>time(NULL) = 1074265801 >>read(0, ". login cyrus secret1\r\n", 4096) = 23 >>socket(PF_UNIX, SOCK_STREAM, 0) = 10 >>connect(10, {sa_family=AF_UNIX, path="/var/run/sasl2//mux"}, 110) = 0 >>writev(10, [{"\0\5cyrus\0\7secret1\0\4imap\0\0", 24}], 1) = 24 >>read(10, "\0\2", 2) = 2 >>read(10, "OK", 2) = 2 >>close(10) = 0 >>select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout) >>write(1, ". NO Login failed: can\'t request"..., 63) = 63 >>time(NULL) = 1074265801 >>select(1, [0], NULL, NULL, {1800, 0} >> >>using cyrus-sasl-2.1.7 >> >> >> >> > Not sure how applicable this will be, but in cyrus 2.2.1 and 2.2.2 using > saslauthd 2.1.15 I have no problem at all using saslauthd -> pam -> > pam_mysql -> mysql
IIRC Cyrus IMAPd 2.2.2 with 'saslauthd -> pam_something' uses cyrus-sasl >= 2.1.15! I have verified this some time ago and I expect it's still the same with 2.2.3. Simon > > Eric > > --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html