Tristan OTierney said: > This is a unique error I believe, because I've > searched the FAQ, and read many posts on the users > list but haven't heard of anyone with a problem > similar to this.<br><br> > > Often when people try and visit my webmail, they get > errors resembling this: > http://otierney.net/images/squirrelerror.jpg > > This happens irreguardless of the browser, so it's > definatly a squirrel mail issue. This also happens > ONLY with squirrelmail, because i've never in 8 months > experienced a problem like this on any of our 20 > domains hosted on this machine. > > I've had this problem with squirrelmail 1.2 and 1.4. > I'm running courier-imap and qmail with vmailmgr. > It's possible that one of those (qmail, vmailmgr, > courier-imap) is causing the problem but it's hard to > say. > > Here's why i think it's squirrel mail though. I > turned courier-imap's # of allowed daemons to 500. I > enabled up to 40 connections per ip, and i even ran > imapproxy. I'm also running php-accelerator and > mod_gzip. So with all those things enabled, i > shouldn't be getting timeouts like this :). I've also > never had timeout issues with standalone clients > (Mail.app, Mozilla Mail, Outlook). > > So has anyone heard of this problem? The only way to > fix it is to refresh the browser window 2-3 times. > It's blazing fast, but it also blazingly times out > (the timeout occurs instantly and i can refresh 1-3 > times to get it to load properly). To make matters > weirder, it's random. It will be fine for a few > minutes, then it will start giving these errors. > > __________________________________ > Do you Yahoo!? > Yahoo! SiteBuilder - Free, easy-to-use web site design software > http://sitebuilder.yahoo.com I have had similar errors with perl generated pages when they are on the secure server (i.e., https//...). We finally traced it down to a bug in certain versions of Internet Explorer which were trying to use connections which were no longer active to the secure server. The basic problem is that it takes quite a while for the browser and the secure server to set up an SSL connection so they try to re-use the connections when talking to the same browser. For example after the page is passed then reuse the connection to send a graphic, etc. The problem is IE doesn't handle the case where the webserver has dropped the connection and IE goes to re-use it. This error will result. Bottom line, check you version of webserver to see if there are any work arounds for the problem. I don't think its really a SM issue. But I'm not a PHP expert.
William R. Mussatto, Senior Systems Engineer Ph. 909-920-9154 ext. 27 FAX. 909-608-7061 ------------------------------------------------------- This SF.net email is sponsored by Dice.com. Did you know that Dice has over 25,000 tech jobs available today? From careers in IT to Engineering to Tech Sales, Dice has tech jobs from the best hiring companies. http://www.dice.com/index.epl?rel_code=104 -- 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
