Tom Collins wrote:
I had something odd happen on my toaster today.
Courier-IMAP stopped accepting connections from localhost. I have no idea why, but restarting it (/etc/init.d/courier-imap restart) appeared to take care of the problem -- it started accepting connections again.
But, I then had trouble with SquirrelMail working. My logs would show a sequence like this:
Feb 16 11:06:13 rusty imapd: Connection, ip=[::ffff:127.0.0.1]
Feb 16 11:06:13 rusty imapd: LOGIN, [EMAIL PROTECTED], ip=[::ffff:127.0.0.1], protocol=IMAP
Feb 16 11:06:13 rusty imapd: LOGOUT, [EMAIL PROTECTED], ip=[::ffff:127.0.0.1], headers=0, body=0, time=0
Feb 16 11:06:13 rusty imapd: Connection, ip=[::ffff:127.0.0.1]
Feb 16 11:06:13 rusty imapd: LOGIN, [EMAIL PROTECTED], ip=[::ffff:127.0.0.1], protocol=IMAP
With the second LOGIN hanging until SquirrelMail timed out.
I tried restarting apache (apachectl graceful), but eventually, I had to reboot the server. Now, everything is working fine, but I'm wondering what could have happened and how I can avoid it in the future. Is there a possibility that a component of courier-imap doesn't get reset properly by the init.d/courier-imap script?
Any thoughts?
Yeah, check your MAXPERIP setting in /usr/lib/courierimap/etc/imapd. It defaults to 4, and you need to raise that to meet your max connections setting if you use SquirrelMail, as ALL connections are from the same IP.
Regards,
Bill
