On Sat, May 28, 2005 at 08:42:59AM -0400, Guido R. Rolon A. wrote:
--with-authdaemonvar=/usr/local/var/spool/authdaemon
...
May 26 21:25:18 mail authdaemond.plain: found pop3pw in userdbshadow
...
May 26 21:10:36 mail sqwebmaild: authdaemon: s_connect() failed: No such
file or directory
You are running the wrong bits together.
sqwebmail-5.x needs courier-authlib to authenticate. It looks like you are
running an old version of courier-imap, which has a built-in authentication
library.
I'm surprised that ./configure didn't give you an error that it couldn't
find courierauthconfig.
In any case, you *might* be able to get it to work by messing with
authdaemonvar, although it's a totally unsupported configuration.
You could try setting sqwebmail to have a single sqwebmaild child (instead
of the default 5), trace it with strace, and find out exactly what file
s_connect is trying to open (i.e. where sqwebmail thinks the socket is).
Then alter authdaemonvar appropriately, or insert a symlink.
As I say, this is *not* a supported configuration; if you want something
that will definitely work, then build courier-authlib and then sqwebmail.
You'll end up with two sets of authdaemons running, one for your (old)
courier-imap popd, and one for your (new) sqwebmail.
If you also rebuild courier-imap as version 4.x, then it will share the
authdaemon.
HTH,
Brian.