> Hi > > Can anyone give me some guidance as to how I can get some sort of debug > information from SquirrelMail to let me know what is causing a login > failure? I'd like to see what SM is thinking the problem is - right now > whenever I try and log in to our test server we just get bounced to > screen saying 'you need to be logged in'. But no clue as to what it > thinks the problem is.
telnet imap-server 143 Check CAPABILITY sting. If you have LOGINDISABLED - you are running system that does not allow plain text logins. SquirrelMail can use plain text login or ssl login when server is running on special port. STARTTLS on 143 port is not supported. Check cookies. SquirrelMail uses them Check your keyboard setting. Letter case and what you enter when you type numbers. Check server logs. SquirrelMail needs write access to temporally directory in order to store session information -- Tomas ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
