Okay -- I've fiddled and tweaked and reconfigured and recompiled, and found this:
The server has several virtual hosts/domains on it. I've now installed SqWebMail in the *.NET domain and web space instead of the traffic-busy *.COM space. In the *.NET space, it's _not_ in a mod_perl area now. I've soft-linked the sqwebmail binary, from its *.NET space location, to /cgi-bin/ of the *.COM area. When invoked via the *.NET:80 URL, SqWebMail runs. When invoked via the *.COM:80 URL/soft-link, it returns the "CGI environment exceeds allowed maximum size" error. Same compiled binary; same Apache; but -with- mod_perl; and different VirtualHost container. I've now also tried -removing- mod_perl from the *.COM:80/cgi-bin/ area, and got the same result -- *.NET works, *.COM does not. I have no idea where to look next. Anyone else...? Thanks kindly, -- Jeff -- On Thu, Dec 04, 2003 at 03:18:37PM -0500, Jeff Gordon wrote: > On Thu, Dec 04, 2003 at 07:14:48AM -0500, Sam Varshavchik wrote: > > Jeff Gordon writes: > > > > >I had SqWebMail 3.6.2 up and running on a new server, yesterday. > > > > > >Then I moved a busy mostly-CGI site to the new server -- and now > > >SqWebMail won't go. It reports (consistently): > > > > > >"The webmail system is temporarily unavailable. An error occured in > > >function CGI: CGI environment exceeds allowed maximum size." > > > > > >Uh, whose "maximum size"? Is this a system variable I don't know > > >about, or a new Apache 2.0 config setting-related maximum, or...? > > > > It's a fixed size of the allowed CGI environment, which includes all CGI > > environment variables. This is an sqwebmail limit. Set by SOCKENVIRONLEN > > in sqwebmail.h. The default of 4096 bytes should be plenty sufficient. > > Even under SSL you shouldn't be anywhere close to that. > > Thanks, Sam (and thanks also to JAB, Brian, and Terry :-) -- > > I _am_ trying to run it under SSL, but I'm puzzled that it was okay a > day ago under the same Apache 2 settings on RH 9, etc., but is not okay > now that folks have started sending browser requests to the site. > > That is, as far as I'm aware, everything is the same now as it was > then, only additional real-time requests are being made of Apache now > but weren't before. Most of those are for a Perl-based CGI 'forum' > script (under mod_perl). > > Is it possible the error message is being triggered by something else, > signifying something other than what it says...? > > -- > > -- Jeff -- <http://www.wellnow.com> > > "There's nothing left in the world to prove. All that's worth doing > is to love one another, using whatever means are available to serve." > > > > -- -- Jeff -- <http://www.wellnow.com> "There's nothing left in the world to prove. All that's worth doing is to love one another, using whatever means are available to serve."
