Oh, BTW, I fixed it. > -----Original Message----- > From: Dustin Puryear [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 20, 2001 2:54 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: RE: [brluglist] Problems with user authentication and Cyrus > IMAP > > > Tim, this was a test account. And no, it doesn't use /etc/securetty. > > Regards, Dustin > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Tim Fournet > Sent: Wednesday, December 19, 2001 3:05 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: [brluglist] Problems with user authentication and Cyrus IMAP > > > Does it work with non-root users? I don't know if /etc/securetty > applies to cyris, and it's really not a good idea to have mail > delivered to root or login to imap as root anyway. It should be > forwarded to another account. > > -Tim > > > On Wed, 2001-12-19 at 14:02, Dustin Puryear wrote: > I am setting up Cyrus, cyrus-imapd-2.0.16_1, on a FreeBSD 4.4-RELEASE box > with cyrus-sasl-1.5.24_8 RFC 2222 SASL. Both were installed via > the FreeBSD > ports tree (recently cvsup'd). For some reason I am unable to > login using my > test accounts. Cyrus is reporting bad passwords. I am unsure what to do at > this point, and have found no documentation to help in > troubleshooting this. > Any help is appreciated! > > First, I did create the accounts and set the passwords: > > mail# cyradm -u mailadmin mail > Please enter your password: > Dec 19 13:48:59 mail imapd[11595]: login: mail.example.com[10.0.0.5] > mailadmin DIGEST-MD5 User logged in > mail.example.com> lm > user.root > mail.example.com> exit > > mail# sasldblistusers|grep root > user: root realm: mail.example.com mech: DIGEST-MD5 > user: root realm: mail.example.com mech: PLAIN > user: root realm: mail.example.com mech: CRAM-MD5 > > I can log in using the root user account via cyradm: > > mail# cyradm -u root mail > Please enter your password: > Dec 19 13:50:52 mail imapd[11608]: login: mail.example.com[10.0.0.5] root > DIGEST-MD5 User logged in > mail.example.com> lm > INBOX > mail.example.com> exit > > But not by logging in remotely or using imtest: > > mail# telnet localhost 143 > Trying 127.0.0.1... > Connected to localhost > Escape character is '^]'. > * OK mail.example.com Cyrus IMAP4 v2.0.16 server ready > 0001 LOGIN "root" "password" > Incorrect password > 0001 NO Login failed: Incorrect password > ^] > telnet> quit > Connection closed. > > On the console I get: > > Dec 19 11:41:08 mail imapd[1701]: badlogin: > localhost.example.com[127.0.0.1] plaintext root > > The same happens with imtest: > > mail# imtest -p imap -a root -m login mail > C: C01 CAPABILITY > S: * OK mail.example.com Cyrus IMAP4 v2.0.16 server ready > S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID > NO_ATOMIC_RENAME UNSELECT MULTIAPPEND SORT THREAD=ORDEREDSUBJECT > THREAD=REFERENCES IDLE AUTH=DIGEST-MD5 AUTH=CRAM-MD5 > S: C01 OK Completed > Password: > C: L01 LOGIN root {7} > + go ahead > C: <omitted> > Dec 19 11:15:54 mail imapd[1640]: badlogin: mail.example.com[10.0.0.5] > plaintext root Incorrect password > ^C > > Is something not running right? I have both master and pwcheck running: > > root 221 0.0 0.2 996 580 ?? Is 1:50AM 0:00.08 > /usr/local/sbin/pwcheck > cyrus 1165 0.0 0.5 2340 1192 p0- I 3:56AM 0:00.14 > /usr/local/cyrus/bin/master > > Regards, Dustin > > --- > Dustin Puryear <[EMAIL PROTECTED]> > Information Systems Consultant > http://members.telocity.com/~dpuryear > In the beginning the Universe was created. > This has been widely regarded as a bad move. - Douglas Adams > > > ================================================ > BRLUG - The Baton Rouge Linux User Group > Visit http://www.brlug.net for more information. > Send email to [EMAIL PROTECTED] to change > your subscription information. > ================================================ > >
================================================ BRLUG - The Baton Rouge Linux User Group Visit http://www.brlug.net for more information. Send email to [EMAIL PROTECTED] to change your subscription information. ================================================
