Courier Authentication Error
Contents |
how to use courier's debugging features to pinpoint the problem. 1. Turn on debugging For courier-imap, you need to set one of the following values in /usr/local/etc/authdaemonrc: DEBUG_LOGIN=1 # turn on authentication debugging DEBUG_LOGIN=2 # turn on authentication debugging AND show passwords This setting is located at the courier imap log file very end of the configuration file. After changing this setting, restart the authentication daemon
No Error In Imap Command Received By Server.
by running the "authdaemond stop" and "authdaemond start" commands. At this point, all debugging output goes to syslog at level 'debug', debug courier imap which is normally not shown. You will probably need to change your /etc/syslog.conf file to be able to see these messages. If you have an existing entry which says "mail.info" (which means facility 'mail', level imapd: authentication error: no such file or directory 'info' or higher) then you can just change this to "mail.debug". Alternatively you can add a new entry like this: *.debug /var/log/debug Don't forget to create this file, and to send a HUP signal to syslogd to make it re-read its configuration: # touch /var/log/debug # killall -1 syslogd If you don't want to mess around with your syslog configuration, you can also start authdaemond manually, and log its output to
Courier Log Sheet Template
a file: /usr/local/libexec/courier-authlib/authdaemond >filename 2>&1 2. Issue a manual login You can use the authtest command to verify authentication, or go ahead and install Courier-IMAP. For courier-imap, you will get much better information by not using a mail client and manually logging in using 'telnet'. The transcript of this telnet session may give useful information as to what is going on. If you are going to report a problem to the mailing list, you should certainly include this transcript as well as the corresponding debugging output. -- to debug POP3 -- # telnet x.x.x.x 110 user USERNAME pass PASSWORD stat quit -- to debug IMAP -- # telnet x.x.x.x 143 a login USERNAME PASSWORD a examine inbox a logout -- to debug POP3 over SSL -- # openssl s_client -connect x.x.x.x:995 (then use same commands as POP3 example) -- to debug IMAP over SSL -- # openssl s_client -connect x.x.x.x:993 (then use same commands as IMAP example) This isn't an option for sqwebmail of course - just login through the web interface and check the authentication debug log which is generated. 3. Interpret the debug output First, a brief explanation of courier's authentication system. There are a number of standalone authentication modules. An authentication module exists for every authentication method
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more authdaemon: s_connect() failed: no such file or directory about Stack Overflow the company Business Learn more about hiring developers or posting ads courier authdaemon with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system
Authdaemond: Fail, All Modules Rejected
and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top http://www.courier-mta.org/authlib/README.authdebug.html courier-authdaemon not attempting to authenticate imap users up vote 1 down vote favorite We have had a little used mail server running fine for more than a year but earlier today it started to fail to authenticate users occasionally and now it has stopped even trying to authenticate. The messages in the mail log are: www imapd: authdaemon: s_connect() failed: Connection refused www imapd: [Hint: perhaps authdaemond is not running?] http://serverfault.com/questions/243309/courier-authdaemon-not-attempting-to-authenticate-imap-users www imapd: LOGIN FAILED, user=XXX, ip=[::ffff:aaa.bbb.ccc.ddd] www imapd: authentication error: Connection refused But as far as I can see everything is running, it just is not working. Before it failed completely it was cycling through each authentication method before it found the appropriate one, now it does not, apparently, attempt to go through any of them. netstat -napt outputs: tcp 0 0 :::143 :::* LISTEN 25051/couriertcpd ps alx outputs: 5 0 25087 1 20 0 3952 284 - S ? 0:00 /usr/sbin/courierlogger -pid=/var/spool/authdaemon/pid -start /usr/libexec/courier-authlib/authdaemond 4 0 25088 25087 20 0 61320 1472 - S ? 0:00 /usr/libexec/courier-authlib/authdaemond 1 0 25089 25088 20 0 61320 356 - S ? 0:00 /usr/libexec/courier-authlib/authdaemond 1 0 25090 25088 20 0 61320 360 - S ? 0:00 /usr/libexec/courier-authlib/authdaemond 1 0 25091 25088 20 0 61320 368 - S ? 0:00 /usr/libexec/courier-authlib/authdaemond 1 0 25092 25088 20 0 61320 368 - S ? 0:00 /usr/libexec/courier-authlib/authdaemond 1 0 25093 25088 20 0 61320 368 - S ? 0:00 /usr/libexec/courier-authlib/authdaemond I have restarted (more times than I care to remember) courier-authlib and courier-imap, and have now copied the distribution configuration file /etc/authlib/authdeamonrc.dist over the /etc/authlib/authdaemonrc file that was in use, although I do not think it had been changed anyway. Telneting to imap port 143 both loca