Hello all, I am trying out the courier-imap proxy feature for the first time as a frontend to multiple courier-imap (qmail) servers. For some reason, it seems like the proxy functionality is not turning on, even though I have set IMAP_PROXY=1 in the imapd config file. For some reason it keeps trying to authenticate locally instead of off the remote server. I have a simple userdb test file set up with this line in it:
[EMAIL PROTECTED] options=mailhost=qmail.webpipe.net Which as far as I can tell from the README.proxy is all I need to have. I have turned on debugging in authlib and get the following output when trying to login through imap on this server: imap imapd: Connection, ip=[::ffff:63.172.124.254] imap authdaemond: received auth request, service=imap, authtype=login imap authdaemond: authuserdb: trying this module imap authdaemond: userdb: opened /etc/authlib/userdb.dat imap authdaemond: userdb: looking up '[EMAIL PROTECTED]' imap authdaemond: userdb: required value 'home' is missing imap authdaemond: authuserdb: REJECT - try next module imap authdaemond: FAIL, all modules rejected imap imapd: LOGIN FAILED, [EMAIL PROTECTED], ip=[::ffff:63.172.124.254] imap imapd: LOGOUT, ip=[::ffff:63.172.124.254], rcvd=46, sent=326 So I add the home value to the userdb, and it wants a uid, so I added all of the values like this: userdb [EMAIL PROTECTED] set home=/home/kevinp mail=/home/kevinp/Maildir uid=500 gid=500 and I get in my userdb file: [EMAIL PROTECTED] uid=500|options=mailhost=qmail.webpipe.net|mail=/home/kevinp/Maildir|home=/home/kevinp|gid=500 after running makeuserdb, and trying again, I get the following debug output: imap imapd: Connection, ip=[::ffff:63.172.124.254] imap authdaemond: received auth request, service=imap, authtype=login imap authdaemond: authuserdb: trying this module imap authdaemond: userdb: opened /etc/authlib/userdb.dat imap authdaemond: userdb: looking up '[EMAIL PROTECTED]' imap authdaemond: userdb: home=/home/kevinp, uid=500, gid=500, shell=<unset>, mail=/home/kevinp/Maildir, quota=<unset>, gecos=<unset>, options=mailhost=qmail.webpipe.net imap authdaemond: userdbshadow: entry not found imap authdaemond: authuserdb: sysusername=<null>, sysuserid=500, sysgroupid=500, homedir=/home/kevinp, [EMAIL PROTECTED], fullname=<null>, maildir=/home/kevinp/Maildir, quota=<null>, options=mailhost=qmail.webpipe.net imap authdaemond: authuserdb: clearpasswd=<null>, passwd=<null> imap authdaemond: no password available to compare. imap authdaemond: authuserdb: REJECT - try next module imap authdaemond: FAIL, all modules rejected imap imapd: LOGIN FAILED, [EMAIL PROTECTED], ip=[::ffff:63.172.124.254] So now I am really confused, shouldn't the proxy see the options tag and query the remote server for the authentication? I don't see why it should need anything more then just the one options=mailhost tag or am I missing something here? Thanks for any help/suggestions, Kevin Additional info: CentOS release 4.3 (Final) Installed by rpm, created by non-root user: courier-authlib-0.58-1 courier-authlib-devel-0.58-1 courier-imap-4.1.1-1 courier-authlib-userdb-0.58-1 imapd --version Courier-IMAP 4.1.1/i386-redhat-linux-gnu/Tue Aug 15 17:02:18 MDT 2006 ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
