> > when trying to set up a test account by doing:- > > cyradm -user admin localhost imap > > Please enter your password: > > Please enter your password: > > cyradm: cannot authenticate to server with as admin > > > > when trying to set up a test account by doing:- > > cyradm -user admin -auth login localhost imap > > IMAP Password: > > Login failed: authentication failure at > > /usr/local/lib/site_perl/5.6.1/i386-linux/Cyrus/IMAP/Admin.pm > > line 78 > > cyradm: cannot authenticate to server with login as admin > > > > ... and many more references ;-)
> 0.) > Check the contents of your logfile after you noticed a failed login. > Didn't see that so far. But see above. ;-) tail /var/log/imapd.log Dec 6 10:54:28 aberdeen master[2093]: about to exec /usr/local/cyrus/bin/imapd Dec 6 10:54:28 aberdeen service-imap[2093]: executed Dec 6 10:54:56 aberdeen imapd[1294]: badlogin: localhost.localdomain[127.0.0.1] PLAIN no mechanism available Dec 6 10:54:59 aberdeen master[1207]: process 1294 exited, status 0 Dec 6 10:55:46 aberdeen imapd[1981]: accepted connection Dec 6 10:55:46 aberdeen master[2107]: about to exec /usr/local/cyrus/bin/imapd Dec 6 10:55:46 aberdeen service-imap[2107]: executed Dec 6 10:55:49 aberdeen imapd[1981]: badlogin: localhost.localdomain[127.0.0.1] DIGEST-MD5 authentication failure Dec 6 10:55:55 aberdeen imapd[1981]: badlogin: localhost.localdomain[127.0.0.1] CRAM-MD5 authentication failure [no secret in database] Dec 6 10:55:58 aberdeen master[1207]: process 1981 exited, status 0 > > 0b). > In a different mail i've read something about db issues. Did you create > sasldb with the same version of berkley db you've compiled cyrus and sasl > with? Or is it a relict (again ?, sorry for my bad english!) from a > different version? If so, build a new one. > Cyrus and SASL are now built with the same version of db and these libs > are known to the dynamic linker, right? only libdb3.2 & libdb3.2-devel are installed, no db2/3 stuff. reinstalled openssl, sasl, imapd & postfix to be sure. ran ldconfig as before. > 2.) > > sasldblistusers > > user: admin realm: aberdeen.chstech.co.uk mech: DIGEST-MD5 > > user: admin realm: aberdeen.chstech.co.uk mech: PLAIN > > user: admin realm: aberdeen.chstech.co.uk mech: CRAM-MD5 > > You use your fqdn as realm. Make new entries for user admin with > the -u option of saslpasswd. The perl programs use your hostname as realm. > -> `saslpasswd -u aberdeen -c admin'. > sasldblistusers should list > [...] > user: admin realm: aberdeen mech: DIGEST-MD5 > [...] > then. > Seems to be an issue with cyradm in case the hostname is set to the fqdn. > `hostname` returns aberdeen.chstech.co.uk, i guess, since the login > message of your server shows that. sasldblistusers user: admin realm: aberdeen mech: DIGEST-MD5 user: admin realm: aberdeen mech: PLAIN user: admin realm: aberdeen mech: CRAM-MD5 > Hope i could add something to the existing confusion ;-) > > Best regards, > > --Andreas Amann > [EMAIL PROTECTED] > No changes when running imtest or cyradm. >From another angle, the boss has a cheap NON-STATIC ADSL connection at the moment, and as such, the DNS on the network isn't set up correctly. Could this be the cause of all this bother? However, remember that I am trying all of the above tests on localhost. I still think this is a SASL problem. Craig Skinner -- Get your free email from www.linuxmail.org Powered by Outblaze
