James A Baker writes:Did you make sure to add the new daemon to your startup scripts before restarting?
wich daemon, doesn�t it uses the authdaemon?
The CGI was split (around 3.6.1...??) into a CGI stub and a "sqwebmaild" daemon process that actually does all the heavy lifting for you. -jab
As I said, the "sqwebmaild" daemon. =)
It's a new daemon process that waits for connections from the CGI stub -- which of course listens for the connections from the browsers over HTTP. The requests for pages are forwarded from the CGI stub program to the new daemon.
SqWebMail still uses the authdaemon, yes. But this is a second daemon process that handles all the actual page requests -- or at least it does most of the work involved, after the stub CGI accepts the original incoming connection request.
Details of where the new daemon were installed by your build should be provided at the end of the "make" command, with a new warning stating that you have to install it in your startup scripts.
In my case, it was installed into "/usr/lib/courier/libexec/courier/sqwebmaild" (which is the default for Courier) -- but I use the full install instead of just the SqWebMail install. ... So I think it'd probably be in "/usr/local/sqwebmail/libexec/sqwebmail/sqwebmaild" (or something like that) when installing just the SqWebMail distribution by itself.
The documentation talks about it too of course. Take a look at this URL (which also references paths specific to the full Courier package, rather than just the SqWebMail package) which is from the Courier site:
http://www.courier-mta.org/install.html#webmail
HTH.
-jab
