Benjamin Burkhart a écrit :
> Hi all,
>
> By strace-ing courierpop3login I found out that it wants to open the 
> above socket but that the socket does not exist.
>
> In the logs, this looks like this:
> Feb 24 01:44:57 servername courierpop3login: Connection, 
> ip=[::ffff:myclientIPaddress]
> Feb 24 01:44:59 servername courierpop3login: authdaemon: s_connect() 
> failed: No such file or directory
> Feb 24 01:44:59 servername courierpop3login: LOGIN FAILED, 
> [EMAIL PROTECTED], ip=[::ffff:myclientIPaddress]
> Feb 24 01:44:59 servername courierpop3login: authentication error: No 
> such file or directory
>
> This on a Debian Sarge box. Here's a bit more data:
> root ~ > dpkg --list | grep courier
> ii  courier-authdaemon        0.58-4                               
> Courier authentication daemon
> ii  courier-authlib           0.58-4                               
> Courier authentication library
> ii  courier-authlib-mysql     0.58-4                               MySQL 
> support for the Courier authentication
> ii  courier-authlib-userdb    0.58-4                               
> userdb support for the Courier authenticatio
> rc  courier-authmysql         0.47-4sarge5                         
> Courier Mail Server - MySQL authentication
> ii  courier-base              0.53.3-5                             
> Courier Mail Server - Base system
> ii  courier-imap              4.1.1.20060828-5                     
> Courier Mail Server - IMAP server
> ii  courier-imap-ssl          4.1.1.20060828-5                     
> Courier Mail Server - IMAP over SSL
> rc  courier-mta               0.47-4sarge4                         
> Courier Mail Server - ESMTP daemon
> ii  courier-pop               0.53.3-5                             
> Courier Mail Server - POP3 server
> ii  courier-pop-ssl           0.53.3-5                             
> Courier Mail Server - POP3 over SSL
> ii  courier-ssl               0.53.3-5                             
> Courier Mail Server - SSL/TLS Support
>
> root ~ > grep -v '^#' /etc/courier/authdaemonrc | grep .
> authmodulelist="authmysql"
> authmodulelistorig="authcustom authcram authuserdb authldap authpgsql 
> authmysql authpam"
> daemons=5
> version=""
> authdaemonvar=/var/run/courier/authdaemon
>
> root /etc/courier > grep -v '^#' pop3d | grep .
> PIDFILE=/var/run/courier/pop3d.pid
> MAXDAEMONS=40
> MAXPERIP=4
> POP3AUTH=""
> POP3AUTH_ORIG="PLAIN LOGIN CRAM-MD5 CRAM-SHA1 CRAM-SHA256"
> POP3AUTH_TLS=""
> POP3AUTH_TLS_ORIG="LOGIN PLAIN"
> POP3_PROXY=0
> PORT=110
> ADDRESS=0
> TCPDOPTS="-nodnslookup -noidentlookup"
> LOGGEROPTS="-name=pop3d"
> POP3DSTART=YES
> MAILDIRPATH=Maildir
>
> As you can see, I am authenticating using a mysql database.
>
> Any ideas as to why the socket is missing, who should create it but 
> doesn't? Actually my configuration has been working like a charm until 
> recently ...
>
> Please let me know if you need more information.
>
> Cheers,
> Benjamin.
>
>   
Hi...
Are Authdaemon running ?

HTH.
Jerome Blion.



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to