11 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] sqwebmail error
FromSent OnAttachments
Rui RomãoJan 16, 2006 6:13 am 
Brian CandlerJan 17, 2006 1:56 am 
Rui RomãoJan 17, 2006 6:27 am 
Julie S. LinJan 17, 2006 4:19 pm 
Sam VarshavchikJan 17, 2006 4:44 pm 
Brian CandlerJan 18, 2006 12:56 am 
Rui RomãoJan 19, 2006 9:35 am 
Brian CandlerJan 20, 2006 12:33 am 
Rui RomãoJan 20, 2006 4:31 am 
Rui RomãoJan 20, 2006 4:39 am 
Brian CandlerJan 21, 2006 1:38 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [sqwebmail] sqwebmail errorActions...
From:Brian Candler (B.Ca@pobox.com)
Date:Jan 18, 2006 12:56:51 am
List:net.sourceforge.lists.courier-sqwebmail

On Tue, Jan 17, 2006 at 04:19:34PM -0800, Julie S. Lin wrote:

Hi

why do I get this error?

The webmail system is temporarily unavailable. An error occured in function /usr/lib/courier/var/sqwebmail.sock CRIT: Several attempts were necessary to connect to sqwebmaild CRIT: Consider increasing the number of pre-forked sqwebmaild processes

my DocumentRoot is /var/www/html ; url I'm using is https://mail.myserver.com

You have some mod_rewrite trickery to map the document root to the webmail CGI? If so, I wonder whether all the image requests end up getting mapped to this too (i.e. https://mail.myserver.com/sqwebmail/foo.png) in which case the CGI will be handling a lot more requests than it should be.

however, when I use https://mail.myserver.com/cgi-bin/webmail everything works beautifully, very odd.

If you are doing rewrite tricks, you could try turning them off, and then inserting an index.html or index.asis which simply redirects the browser to https://mail.myserver.com/cgi-bin/webmail

(This has the secondary advantage that if they go to http://mail.myserver.com/ they'll be forced to use https)

Brian.