On Thu, 2005-03-31 at 18:05 +0200, Andreas Haase wrote: > Hi, > > I have a cyrus 2.1.15 running on Suse 9.0. It authenticates againt sasl2 > (saslauthd), which uses ldap to get the credentials. And now, if I put in > invalid usernames or passwords, I get the following outout: > > --- snip --- > mail:~ # telnet localhost 110 > Trying ::1... > telnet: connect to address ::1: Connection refused > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > +OK mail Cyrus POP3 v2.1.15 server ready <[EMAIL PROTECTED]> > user foo > +OK Name is a valid mailbox > pass foo > | > [EMAIL PROTECTED] > [EMAIL PROTECTED]@ÃJ@: Successful return: 0 > Successful return: 0 > -ERR [AUTH] Invalid login > --- snap --- > > Could anyone please tell me where the crap between the pass line and error > message is coming from? Any hints appreciated. If you need more infos, > please let me know. ---- from my past experience with debugging login problems (adjust for pop3 instead of imap - my problem was using IMP with imap login).
I was able to capture with just a few slight adjustments... captured successful login via 'telnet localhost 143' # tcpdump -w /tmp/imp-imap.good -i lo -s 0 'port imap' captured unsuccessful login via 'imp' at the moment the 'admin' tried to do it's thing # tcpdump -w /tmp/imp-imap.tcpdump -i lo -s 0 'port imap' and then 'tethereal -r /tmp/imp-imap.[tcpdump|good] showed me the difference...turns out - even though IMP is configured to send imap/notls, admin login is encrypted. Craig --- 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
