On Tue, Mar 08, 2005 at 06:30:09PM -0500, Sam Varshavchik wrote......
> Jacob Friis Larsen writes: > > >>> If I go to http://192.168.130.10/cgi-bin/sqwebmail/ I get "Internal > >>Error > >>> > >>> The webmail system is temporarily unavailable. An error occured in > >>> function write: Transport endpoint is not connected" > >>> > >>> Any idea what I have done wrong and where to look? > >> > >>You need to start sqwebmaild. See INSTALL. > > > >It is started. I see it in ps aux > > The above error is reported when the sqwebmail cgi-bin stub cannot > connect to the socket that sqwebmaild is listening on. > > The most common reason is that sqwebmaild is not running, but you > claim that it is. > > The second most common reason is that the permissions on the cgi-bin > stub binary are wrong. The cgi-bin stub must be setuid root. I just built a new email server using courier/sqwebmail and had the same problem. My build was on a debian box so everything came in .deb packages, but I believe upstream source downloads might have the same problem. Anyway, the process ID's for all courier programs reside in /var/run/courier. In my build of courier, the default permissions for /var/run/courier were 770 with uid/gid of daemon.daemon. Getting sqwebmail to run was solved by ... chmod 755 /var/run/courier Indeed, I checked an old email server that has been running courier/sqwebmail for a long while now, and its permissions were 755, not 770 as in the default build. FYI there is a bug filed already in the Debian BTS for this. Kevin
signature.asc
Description: Digital signature
