Re: [SM-USERS] FYI: inetd, imap2, and squirrelmail

2002-11-05 Thread David Dooling
Chris Hilts said: >> inetd[200]: imap2/tcp server failing (looping), service terminated > > You can expect a significant performance increase from SquirrelMail if > you modify your configuration so that your imapd is always ready, and > not being started by inetd. Will do... or not. I cannot

Re: [SM-USERS] FYI: inetd, imap2, and squirrelmail

2002-11-05 Thread David Dooling
Chris Hilts said: >> inetd[200]: imap2/tcp server failing (looping), service terminated > > You can expect a significant performance increase from SquirrelMail if > you modify your configuration so that your imapd is always ready, and > not being started by inetd. Will do. dd -- David Doolin

Re: [SM-USERS] FYI: inetd, imap2, and squirrelmail

2002-11-05 Thread Chris Hilts
> inetd[200]: imap2/tcp server failing (looping), service terminated You can expect a significant performance increase from SquirrelMail if you modify your configuration so that your imapd is always ready, and not being started by inetd. Plus you avoid problems like the one you experienced.

[SM-USERS] FYI: inetd, imap2, and squirrelmail

2002-11-05 Thread David Dooling
I am posting this because I was unable to find a suitable solution on google or the mailing list archives. I also sending it to the Debian maintainer in case he wants to show a warning during the install. We have recently begun deploying SM as the standard MUA. We were having some problems which