I try logging in to the POP3 service running courier authdaemon with a MYSQL backend, and a postfix relay, and this shows up in my mail.log. Mar 26 05:07:37 nova courierpop3login: Connection, ip=[::ffff:127.0.0.1] Mar 26 05:07:46 nova courierpop3login: LOGIN: DEBUG: ip=[::ffff:127.0.0.1], command=USER Mar 26 05:07:50 nova courierpop3login: LOGIN: DEBUG: ip=[::ffff:127.0.0.1], command=PASS Mar 26 05:07:50 nova courierpop3login: LOGIN: DEBUG: ip=[::ffff:127.0.0.1], [EMAIL PROTECTED] (not the actual email address I'm trying) Mar 26 05:07:50 nova courierpop3login: LOGIN: DEBUG: ip=[::ffff:127.0.0.1], password=*removed* Mar 26 05:07:50 nova courierpop3login: authdaemon: starting client module Mar 26 05:07:50 nova courierpop3login: authdaemon: TEMPFAIL - no more modules will be tried Mar 26 05:07:55 nova courierpop3login: LOGIN FAILED, ip=[::ffff:127.0.0.1] Mar 26 05:07:58 nova courierpop3login: LOGIN: DEBUG: ip=[::ffff:127.0.0.1], command=QUIT Mar 26 05:07:58 nova courierpop3login: LOGOUT, ip=[::ffff:127.0.0.1]
The configuration file matches exactly the settings I have for MYSQL, and I can log into the server manually with no problem whatsoever. ##NAME: LOCATION:0 # # The server name, userid, and password used to log in. MYSQL_SERVER 127.0.0.1 MYSQL_USERNAME mail_admin MYSQL_PASSWORD removed ##NAME: MYSQL_SOCKET:0 # # MYSQL_SOCKET can be used with MySQL version 3.22 or later, it specifies the # filesystem pipe used for the connection # # MYSQL_SOCKET /var/run/mysqld/mysqld.sock ##NAME: MYSQL_PORT:0 # # MYSQL_PORT can be used with MySQL version 3.22 or later to specify a port to # connect to. MYSQL_PORT 0 ##NAME: MYSQL_OPT:0 # # Leave MYSQL_OPT as 0, unless you know what you're doing. MYSQL_OPT 0 ##NAME: MYSQL_DATABASE:0 # # The name of the MySQL database we will open: MYSQL_DATABASE mail ##NAME: MYSQL_USER_TABLE:0 # # The name of the table containing your user data. See README.authmysqlrc # for the required fields in this table. MYSQL_USER_TABLE users The configuration file was snipped here to make things easier... all the important information for this particular problem's in here, I think. My my.cnf shows MYSQL listening on port 3306 to IP address 127.0.0.1. Changing the MYSQL_PORT setting in the config file didn't fix the error, so I changed it back to 0. Netstat -a shows the following: tcp 0 0 localhost:mysql *:* LISTEN Running authtest wasn't overly helpful, neither was tossing the error in the above snip from mail.log into search engines. I'm running Courier v0.47 on Ubuntu 6.06 if that's any help. I had a look at some of the pages on courier-mta.org already, though while they bring up that error message, everything they say to look for and double check is already the way it should be. Have I missed something overly obvious, perhaps? James ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
