On Fri, 16 Jan 2004, Ken Murchison wrote: > Carsten Hoeger wrote: > > > On Thu, Jan 15, Rob Siemborski wrote: > > > > > >>I'm quite pleased to announce the long-awaited stable release of Cyrus > >>IMAPd 2.2.3. This release contains substantial new features over the 2.1 > >>series including extensive support for mailbox annotations, NNTP, much > >>more stable process accounting, and of course, virtual domains. > > > > > > 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 > > 2.1.7 or 2.1.17? I just went through the trouble of configuring > pam_mysql (0.4.7) for use with saslauthd (2.1.17) and it works fine with > Cyrus 2.2.3. If you share your config, perhaps we can help.
This works only for unqualified users. saslauthd pam module ignores realms. -- Igor