When you configure courier, you need to make sure it links with vpopmail authentication and not mysql. so when you configure courier be sure to pass the option --without-authmysql and also --with-authvchkpw. I ran configure on my qmail server with vpopmail/courier/mysql with the following arguments:
# ./configure --disable-root-check --without-authdaemon --without-authmysql --with-authvchkpw --enable-workarounds-for-imap-client-bugs then once built, you need to make the following changes. Edit /usr/lib/courier-imap/etc/imapd Change 'AUTHMODULES="..."' to 'AUTHMODULES="authvchkpw"' Change 'IMAPDSTART=NO' to 'IMAPDSTART=YES' As far as getting qmailadmin to work with mysql, there shouldnt be any problems there, so if qmailadmin can't authenticate, theres something wrong with your vpopmail. When compiling vpopmail make sure you edit the mysql.h file to use the correct mysql host/user/pass, and also make sure you give the --enable-mysql=y when configuring vpopmail. If it still fails, the only other thing i can think of is that the mysql user which vpopmail uses, doesnt have the required rights it needs to edit the vpopmail db. On Fri, 2003-06-27 at 23:17, Michael Bowe wrote: > > That's interesting, Tom. I created a new domain called 'test1.com' and a > new user > > called 'test' and all the records in the database work and POP mail works > fine, > > however, Qmailadmin and IMAP won't authenticate. > > > > I double-checked the info for that domain/user on the command line and > vuserinfo > > reports back the correct information. > > Not sure if this is your problem, but it is something that trips a lot of > people up... : > > Every time you recompile vpopmail, you then need to go and recompile any > of the other apps that make use of the vpopmail authentication libraries > (eg qmailadmin, courier-imap) > > Michael. > >
