Please respond to list. This is very useful info for other people with your problem.
>>Please include log snippets. There's no reason why SM would corrupt >>other IMAP sessions, but who knows. Also, have you tried logging in to >>IMAP on the command line yourself to see what happens? >> > > It's OK - I think I've sorted it, with the help of the folks on IRC > (thanks!). It was a combination of two things: > > 1) MAXPERIP in Courier's imapd config was set far too low. The default > of 4 might be suitable for remote users, but it doesn't take much for SM > to make more connections than that! Unless you use imapproxy, which you also might want to consider. > 2) To confuse matters, Konqueror (my test browser) didn't seem to be > clearing out the SM session cookie properly when I clicked Sign Out. > This led to spurious login failures for other users. > > I've updated the logging-in-problems wiki on the website to reflect > this... Thanks. - paul ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com -- 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
