Hi Bill: Thanks for responding. The optimizer is a good suggestion which should help. But maybe I didn't make myself clear. SquirrelMail runs just fine and is snappy from WITHIN our network but is very slow only when using a browser from OUTSIDE of our network. It is running on a very fast test server with plenty of memory, fast SCSI drives and only a few mail accounts. There is no encryption. The network has plenty of spare capacity and bandwidth to the internet and is otherwise very fast.
I guess I'm wondering if everyone is happy with squirrelmail's performance for use as a remote webmail system or whether they see it as slow also. If the list says SM should be quick when used remotely then we probably screwed up the install or have too many plug-ins and we'll set it up again. It just seems as if there's a lot of back-and-forth communications between the browser and squirrelmail before a page is loaded or refreshed. -----Original Message----- From: Bill Shupp [mailto:[EMAIL PROTECTED] Sent: Monday, May 31, 2004 10:40 PM To: [EMAIL PROTECTED] Subject: Re: [toaster] SquirrelMail is very slow Jeff Koch wrote: > > Hi All: > > We have the standard toaster setup with courier-imap and squirrelmail. > We are finding that although squirrelmail has acceptable performance > from web browsers within our network it is agonizingly slow when > accessed outside of our network - even from high speed connections. We > have plenty of spare bandwidth on our network and everything else (web > sites, etc.) work quickly. We also have squirrelmail running on the > same server as courier-imap. > > Squirrelmail seems to be generating fairly lite-weight web pages so we > are at a loss to understand why it runs so slow from outside our > network. Could there be numerous and very large cookies being stored > on the browsing pc? We do have a number of plug-in modules installed > in SM but that should produce the same load within the network. > > What are other people seeing? or should we just switch to SqWebMail? > > > Best Regards, > > Jeff Koch There are a few things to consider: 1. Is it behind SSL? If so, you might consider also offering it unencrypted. This can be a BIG slow down. 2. Try increasing the MAXDAEMONS and MAXPERIP in courier-imap. If you are worried about DOS attacks from the outside, then only offer it on localhost, or setup multiple instances of courier-imap. Also, try using authdaemon, and crank up the number of authdaemons as well. I've found this to help a lot, as it caches logins. 3. Lastly, PHP is an interpreted language, and can be slow under heavy loads. You could look into a PHP "optimizer", and there are some mentioned on the SquirrelMail site. I have no experience with them, however. I've used the first 2 options above to squeeze much more of hardware. But ultimately, you might just need more hardware. Regards, Bill Shupp
