Hi all... I'm running the following versions:
courier-imap 4.1.1-1
courier-authdaemon 0.47-13
courier-base 0.53.2-1
courier-authlib 0.58-2
courier-authlib-userdb 0.58-2
This is a Debian "unstable" system. I apologize if some of the
package/versions don't make sense out of a Debian context.
My authdaemonrc has
authmodulelist="authuserdb"
and I have (what looks to be) a properly-configured user homedir and
/etc/courier/userdb file. I have made my hashes.
imapd is listening on the loopback address, and I'm testing from the
same host. I've tried with iptables cleared to no effect.
I telnet to localhost:143, issue my
A LOGIN [EMAIL PROTECTED] password
But the telnet client immediately quits:
Connection closed by foreign host.
In syslog I see (long lines, sorry):
Jun 6 17:52:27 mushroom imapd: Connection, ip=[::ffff:127.0.0.1]
Jun 6 16:52:27 mushroom imapd: LOGIN: ip=[::ffff:127.0.0.1], command=LOGIN
Jun 6 16:52:27 mushroom imapd: LOGIN: ip=[::ffff:127.0.0.1], [EMAIL
PROTECTED]
Jun 6 16:52:27 mushroom imapd: LOGIN: ip=[::ffff:127.0.0.1], password=test
Jun 6 16:52:27 mushroom authdaemond.plain: received auth request,
service=imap, authtype=login
Jun 6 16:52:27 mushroom authdaemond.plain: authuserdb: trying this module
Jun 6 16:52:27 mushroom authdaemond.plain: userdb: opened
/etc/courier/userdb.dat
Jun 6 16:52:27 mushroom authdaemond.plain: userdb: looking up '[EMAIL
PROTECTED]'
Jun 6 16:52:27 mushroom authdaemond.plain: userdb:
home=/home/vmail/example.com/user, uid=1005, gid=1005, shell=<unset>,
mail=/home/vmail/example.com/user/Maildir, quota=<unset>, gecos=<unset>,
options=<unset>
Jun 6 16:52:27 mushroom authdaemond.plain: found imappw in userdbshadow
Jun 6 16:52:27 mushroom authdaemond.plain: authuserdb:[EMAIL PROTECTED],
sysuserid=1005, sysgroupid=1005, homedir=/home/vmail/example.com/user, [EMAIL
PROTECTED], fullname=<null>, maildir=/home/vmail/example.com/user/Maildir,
quota=<null>, options=<null>
Jun 6 16:52:27 mushroom authdaemond.plain: authuserdb: clearpasswd=<null>,
passwd=$1$0IZgcU/P$/wX1Jv7lt/tA2jRIwyzyD1
Jun 6 16:52:27 mushroom authdaemond.plain: password matches successfully
Jun 6 16:52:27 mushroom authdaemond.plain: authuserdb: ACCEPT, username
[EMAIL PROTECTED]
Jun 6 16:52:27 mushroom imapd: getpwnam: Success
Note that I've blocked out the email address so as not to feed the spambots.
For completeness' sake, authdaemon correctly rejects me when the
password is worng or when a bogus user logs in.
You can see that while imapd logs the opening of the connection, the
log is completely uninformed about the connection's closure.
What's going wrong with imapd? Why isn't it progressing on beyond
invocation of authdaemon?
How do I get more info about what imapd is doing and why it wants to
close the connection?
The Courier docs indicate that putting a
DEBUG_LOGIN=2
at the bottom of the imapd config file will work just like in
authdaemonrc config, but this in fact has no effect on my imapd.
Thanks in advance...
--
Christopher DeMarco <[EMAIL PROTECTED]>
Alephant Systems (http://alephant.net)
PGP public key at http://pgp.alephant.net
+1-412-708-9660
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
