courier-imap

cs-cam · 06-07-2006, 08:15 AM

Hey,

Could anyone give me a hand debugging my courier-imap problem? I've set up Postfix and courier-imap to replace Qmail and it's not letting me log in. I'll post some basics of my setup, I'm using MySQL for authlib.

Running daemons (checked with ps):
mysqld
courier-authlib
courier-imapd-ssl
postfix

authdaemonrc:

Code:

authmodulelist="authmysql"
authmodulelistorig="authuserdb authshadow authpgsql authldap authmysql authcustom"
daemons=5
authdaemonvar=/var/run/courier
DEBUG_LOGIN=2
DEFAULTOPTIONS=""

authmysqlrc:

Code:

MYSQL_CRYPT_PWFIELD	password
MYSQL_DATABASE		****
MYSQL_GID_FIELD		'73'
MYSQL_HOME_FIELD	'/var/spool/mail/'
MYSQL_LOGIN_FIELD	username
MYSQL_MAILDIR_FIELD	maildir
MYSQL_NAME_FIELD	name
MYSQL_OPT		0
MYSQL_PASSWORD		****
MYSQL_SERVER		localhost
MYSQL_UID_FIELD		'73'
MYSQL_USERNAME		****
MYSQL_USER_TABLE	mailbox

Sample log when I try to log in (verbose isn't in these guys dictionary):

Code:

Jun  7 22:56:24 marvin imapd-ssl: Connection, ip=[::ffff:192.168.1.1]
Jun  7 22:56:24 marvin imapd-ssl: LOGIN FAILED, method=PLAIN, ip=[::ffff:192.168.1.1]
Jun  7 22:56:29 marvin imapd-ssl: LOGIN FAILED, user=me@camdaniel.com, ip=[::ffff:192.168.1.1]
Jun  7 22:56:37 marvin imapd-ssl: LOGOUT, ip=[::ffff:192.168.1.1], rcvd=101, sent=352

I've tried connecting directly on the port using openssl and it won't let me login. The database schema is referred to correctly in authmysqlrc, the file contains no spaces (only tabs) and in the database I'm using boring old MD5() for the password. Any ideas at all? Even a way to make it print semi-useful logs, I've been at this for hours and I can't make any sense of it, the password is correct I'm 100% sure of that.

I'm hoping I'm over looking something simple, Postfix works fine I can see in the logs that it's receiving mail fine but I just can't login to the IMAP server to read it

Any ideas, tips, pointers would be greatly appreciated

MasterC · 06-08-2006, 03:34 AM

A quick guess would be something wrong somewhere in your conf's because it appears to be trying to login using "Plain" authentication (that's how I read it anyway).

What I would do is narrow it down:

I'd go basic, and gradually more complex. So, I would:

Switch to basic authentication, for me this was pam:
authdaemonrc:
authmodulelist="authpam"

Adjust your other conf's to agree with this change, and check it. If it doesn't work then either, and you are getting the same error, then the problem may not be with the auth, but somewhere else (maybe an oversite in Postfix's setup, some settings for mysql are in there).

Just my quick thoughts, I hate when I have these things happen to me! Good luck, and please follow up if you get it going, it's always nice to have these kinds of things documented and easy to find.

Cool

cs-cam · 06-09-2006, 01:52 AM

I figured it out today

Quote:

Originally Posted by mysql

I'm using boring old MD5() for the password.

I was sure I read a guide somewhere that claimed Courier supported a few different hashing methods and could automatically detect which one was being used based on hash length and some other things so I picked MD5 because I've used it before for a lot of things. Turns out either that was incorrect or the Frugalware version of courier-authlib is compiled funny but changing the passwords in the DB to ENCRYPT()'ed fixed the problem :/

Either way I'm happy, now I have IMAP which means I can host my parents email as they travel a bit these days and prefer webmail