25 messages in net.sourceforge.lists.courier-users[courier-users] Can't log in via cour...
FromSent OnAttachments
James HomuthMar 26, 2007 2:56 am 
Bernd WurstMar 26, 2007 3:52 am 
Bernd WurstMar 26, 2007 3:54 am 
James HomuthMar 26, 2007 3:57 am 
Bernd WurstMar 26, 2007 4:02 am 
James HomuthMar 26, 2007 5:08 am 
Gordon MessmerMar 26, 2007 8:25 am 
James HomuthMar 26, 2007 8:48 am 
Gordon MessmerMar 26, 2007 9:34 am 
James HomuthMar 26, 2007 5:51 pm 
Gordon MessmerMar 26, 2007 9:57 pm 
Bernd WurstMar 26, 2007 10:35 pm 
James HomuthMar 27, 2007 3:19 am 
Gordon MessmerMar 27, 2007 6:46 am 
James HomuthMar 27, 2007 8:52 am 
Bernd WurstMar 27, 2007 10:29 am 
James HomuthMar 28, 2007 3:39 pm 
Bernd WurstMar 28, 2007 10:42 pm 
James HomuthMar 31, 2007 4:21 am 
James HomuthMar 31, 2007 4:25 am 
Bernd WurstMar 31, 2007 6:54 am 
James HomuthMar 31, 2007 7:32 am 
Bernd WurstMar 31, 2007 7:42 am 
James HomuthMar 31, 2007 9:05 am 
James HomuthMar 31, 2007 9:12 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Can't log in via courier-pop3Actions...
From:James Homuth (jam@the-jdh.com)
Date:Mar 26, 2007 2:56:24 am
List:net.sourceforge.lists.courier-users

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], username=my@test.user (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