Thanks Brian.. I checked everything. Is this a firewall/linux issue ?
My error specifically says "Connection refused"
Dec 2 05:53:25 yukon sqwebmaild: authdaemon: s_connect() failed: Connection refused
-----
here are my attempts:
-----
00. Dropped the firewall and everything else
-----
01. Searched the whole code for the word "refused".
[EMAIL PROTECTED] sqwebmail-3.6.2]# grep -i -r refused *
NOTHING..
-----
02. Searched the whole code for authdaemon syslog messages
Could not find the words "Connection Refused" anywhere..
[EMAIL PROTECTED] sqwebmail-3.6.2]# grep -i -r "authdaemon:" *
authlib/authdaemon.c: "authdaemon: pipe() failed");
authlib/authdaemon.c: "authdaemon: failed to execute " PROG);
authlib/authdaemon.c: "authdaemon: wait() failed");
authlib/authdaemonlib.c: syslog(LOG_CRIT, "authdaemon: socket() failed: %m");
authlib/authdaemonlib.c: syslog(LOG_CRIT, "authdaemon: s_connect() failed: %m");
authlib/authdaemond.c: syslog(LOG_ERR, "authdaemon: Bad line in %s: %s\n",
authlib/authdaemond.c: syslog(LOG_INFO, "authdaemon: modules=\"%s\", daemons=%u\n",
authlib/authdaemond.c: syslog(LOG_CRIT, "authdaemon: malloc() failed: %m");
authlib/authdaemond.c: syslog(LOG_CRIT, "authdaemon: fork() failed: %m");
authlib/authdaemond.c: syslog(LOG_CRIT, "authdaemon: pipe() failed: %m");
authlib/authdaemond.c: syslog(LOG_CRIT, "authdaemon: fcntl() failed: %m");
-----
03. Checked authmodulelist
[EMAIL PROTECTED] sqwebmail-3.6.2]# cat authmodulelist
authdaemon
-----
04. Checked the compiled modules
[EMAIL PROTECTED] sqwebmail-3.6.2]# cat authmodulelist
authdaemon
-----
05. Checked the rc file
cat ./authlib/authdaemonrc
#authmodulelist="authcustom authcram authuserdb authvchkpw authldap authpam"
authmodulelist="authvchkpw"
(I changed it to only vpopmail)
-----
06. Checked the compiled modules
[EMAIL PROTECTED] sqwebmail-3.6.2]# ./authlib/authinfo
AUTHENTICATION_MODULES="authdaemon"
AUTHDAEMONMODULELIST="authcustom authcram authvchkpw authldap authuserdb authpam"
SASL_AUTHENTICATION_MODULES="CRAM-SHA1 CRAM-MD5 PLAIN LOGIN"
-----
Any help would be greatly appreciated..
Glow
--------------------------------------------------
----- Original Message -----
From: "Brian Candler" <[EMAIL PROTECTED]>
To: "zanchu_ml_01 @ hotmail_com" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, December 01, 2003 11:37 AM
Subject: Re: [sqwebmail] yukon sqwebmaild: authdaemon: s_connect() failed: Connection
refused
On Mon, Dec 01, 2003 at 11:11:01AM -0800, zanchu_ml_01 @ hotmail_com wrote:
> At the risk of asking a dumb question.. my sqwebmail
> has suddenly stopped working.. Can someone point me
> to the right place in the archives ? I'm running
> version sqwebmail-3.6.2
First thing to try is to stop and start authdaemon (see the section
"Post-install configuration" in the document INSTALL in the top level of the
sqwebmail source)
> Here are my authorization settings
> ----------
> grep 'AUTHMODULES' /usr/lib/courier-imap/etc/imapd
> ##NAME: AUTHMODULES:0
> #AUTHMODULES="authuserdb authvchkpw authshadow"
> AUTHMODULES="authuserdb authvchkpw authshadow relay-ctrl-allow"
> ##NAME: AUTHMODULES_ORIG:0
> #AUTHMODULES_ORIG="authuserdb authvchkpw authshadow"
> AUTHMODULES_ORIG="authuserdb authvchkpw authshadow
> ----------
Err, well that's the 'imapd' config file, but this is the sqwebmail mailing
list, and the error you report is from sqwebmail too:
> tail /var/log/messages file..
> Dec 1 10:46:18 ykon sqwebmaild: authdaemon: s_connect() failed: Connection
> refused
> ----------
In your sqwebmail config files directory you should have a text file called
'authmodulelist', which should be like this:
$ cat authmodulelist
authdaemon
$
Then you need to look at authdaemonrc (in this same directory) to see which
authentication modules sqwebmail's authdaemond is going to use.
Note that if you have both courier-imap and sqwebmail installed, then they
will use separate pools of authdaemond processes, unless you explicitly
configure them at compile time to share the same authdaemon socket.
Regards,
Brian.
