Squirrelmail is REALLY slow lately on my system. When I first installed it, it worked fine, which was about a month ago. Now it takes minutes to log in, and authenticate, get the mailbox list, etc. As of today, it fails completely. For example:

Sep 25 00:57:45 raincross-tech dbmail/imap4[18756]: SS_WaitAndProcess(): client @ socket 3 (IP: 127.0.0.1) accepted Sep 25 00:58:45 raincross-tech dbmail/imap4[18756]: COMMAND: [A001 LOGIN "foo" "bar"] Sep 25 00:58:45 raincross-tech dbmail/imap4[18756]: IMAPD [PID 18756]: user (id:1, name foo) tries login^M Sep 25 00:58:45 raincross-tech dbmail/imap4[18756]: IMAPD [PID 18756]: user (id 1, name foo) login accepted @ 2002-09-25 00:58:45^M Sep 25 00:59:45 raincross-tech dbmail/imap4[18756]: COMMAND: [A002 SELECT "INBOX"]
Sep 25 01:02:46 raincross-tech dbmail/imap4[18756]: COMMAND: [A002]
Sep 25 01:02:46 raincross-tech dbmail/imap4[18756]: COMMAND: [A002]
Sep 25 01:02:46 raincross-tech dbmail/imap4[18756]: imap_process(): error [Broken pipe] on write-stream Sep 25 01:02:46 raincross-tech dbmail/imap4[18756]: SS_WaitAndProcess(): client @ socket 3 (IP: 127.0.0.1) logged out, connection closed

Notice that it took 5 minutes for the above transaction to take place? and the broken pipe error?

Has anyone else run into this?

BTW, I used Eudora to log in via IMAP on the same account and it's nice and fast, so I'm thinking it's probably squirrelmail's IMAP routines that are screwing up.

-Micah

Reply via email to