[courier-users] IMAP LOGIN

[Luigi Bai]

First of all, I know that there are a lot of people using the IMAP server on this list. This is my first time using Courier, and I'm surprised to have this problem.

I'm having a strange problem with IMAP LOGIN. I can run both the IMAP and POP3 servers, and both are using authdaemon/authuserdb. I can log into the POP3 server just fine, but whenever I try to LOGIN to the IMAP server I get the NO reply. This has been tested from various MUAs and by hand.

Here's part of what I tested:

# ./authtest [EMAIL PROTECTED] <password>
Authenticated: module authdaemon
Home directory: /var/mail/boxes/test
UID/GID: <uid>/<gid>
Maildir: /var/mail/boxes/test/Maildir
[EMAIL PROTECTED]
AUTHFULLNAME=<none>

# <path to courier>/sbin/pop3login <path to courier>/libexec/authlib/authdaemon /bin/ls -al
INFO: Connection, ip=[127.0.0.1]
+OK Hello there.
USER [EMAIL PROTECTED]
LOGIN: DEBUG: ip=[127.0.0.1], command=USER
+OK Password required.
PASS <password>
LOGIN: DEBUG: ip=[127.0.0.1], command=PASS
LOGIN: DEBUG: ip=[127.0.0.1], [EMAIL PROTECTED]
LOGIN: DEBUG: ip=[127.0.0.1], password=<password>
total 16
drwx------ 3 courier group 4096 Feb 14 15:07 .
drwxrwxr-x 9 courier group 4096 Feb 14 14:58 ..
-rw-r--r-- 1 courier group 8 Feb 14 15:07 .courier
drwxr-xr-x 5 courier group 4096 Feb 14 15:07 Maildir

# <path to courier>/sbin/imaplogin <path to courier>/libexec/authlib/authdaemon /bin/ls -al
INFO: Connection, ip=[127.0.0.1]
* OK Courier-IMAP ready. Copyright 1998-2003 Double Precision, Inc. See COPYING for distribution information.
LOGIN [EMAIL PROTECTED] <password>
LOGIN: DEBUG: ip=[127.0.0.1], [EMAIL PROTECTED]
LOGIN NO Error in IMAP command received by server.
LOGOUT
LOGIN: DEBUG: ip=[127.0.0.1], command=LOGOUT
* BYE Courier-IMAP server shutting down
LOGOUT OK LOGOUT completed
INFO: LOGOUT, ip=[127.0.0.1]


First, am I doing something wrong? Shouldn't imap and pop3 both point to authdaemon for authentication? Why is it saying "command=<user>" instead of "command=LOGIN"?? Why is the username uppercased; does that matter? Why is there an error in the IMAP command received by the server? If there's a login error, I'd expect NO, and if there's a malformed login command, I'd expect BAD...

For completenes, here's a part of .../etc/imapd:

# grep AUTH imapd
##NAME: AUTHSERVICE:0
# AUTHSERVICE143=imap
# AUTHSERVICE993=imaps
##NAME: AUTHMODULES:0
AUTHMODULES="authdaemon"
##NAME: AUTHMODULES_ORIG:0
AUTHMODULES_ORIG="authdaemon"
IMAP_CAPABILITY="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 IDLE"
IMAP_CAPABILITY_ORIG="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 IDLE"
# with or without TLS then just comment this out, and add AUTH=PLAIN to
IMAP_CAPABILITY_TLS="$IMAP_CAPABILITY AUTH=PLAIN"
IMAP_CAPABILITY_TLS_ORIG="$IMAP_CAPABILITY_ORIG AUTH=PLAIN"

and from pop3d:

# grep AUTH pop3d
##NAME: AUTHMODULES:0
AUTHMODULES="authdaemon"
##NAME: AUTHMODULES_ORIG:0
AUTHMODULES_ORIG="authdaemon"
##NAME: POP3AUTH:1
# To advertise the SASL capability, per RFC 2449, uncomment the POP3AUTH
# POP3AUTH="LOGIN"
# If you have configured the CRAM-MD5 or CRAM-SHA1, set POP3AUTH to something
# POP3AUTH="LOGIN CRAM-MD5 CRAM-SHA1"
POP3AUTH="CRAM-MD5 CRAM-SHA1"
##NAME: POP3AUTH_ORIG:0
POP3AUTH_ORIG="LOGIN CRAM-MD5 CRAM-SHA1"
##NAME: POP3AUTH_TLS:1
# POP3AUTH_TLS environment variable:
# POP3AUTH_TLS="LOGIN PLAIN"
POP3AUTH_TLS=""
##NAME: POP3AUTH_TLS_ORIG:0
POP3AUTH_TLS_ORIG="LOGIN PLAIN"



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users