I dont know if this is what you need, according to previous posts.
Oh, well...
I had a simular problem a while ago. I use qmail-1.03, vpopmail 5.2.1
with mysql as backend. I have --default-domain=domain1.com as option for
my configure script for vpopmail.
All users which were using the default domain, logging in with just
"username" as username, never noticed any problems, _but_ user on my
virtual domains, loging in with "[EMAIL PROTECTED]" had problem
after "a while", depending on the serverload.
After hours, spent on reading mailinglists and various google results, I
figured out that configuring courier-imap like this, skipping any other
autentication module, except from vchkpw, solved the problem;
./configure --enable-workarounds-for-imap-client-bugs \
--disable-root-check \
--without-authpam \
--without-authldap \
--without-authpwd \
--without-authmysql \
--without-authpgsql \
--without-authshadow \
--without-authuserdb \
--without-authcustom \
--without-authcram \
--without-authdaemon \
--with-authvchkpw \
--with-ssl
Good luck!
On Tue, 2002-11-26 at 02:46, Taylor Dondich wrote:
> Well, I attempted to correct the issue; however, courier-imap still
> tends to muck up authentication after awhile (about an hour or so). Is
> there any way to have courier-imap give a bit more verbose error
> messaging. All I see is LOGIN FAILED. I don't know whhy. Also, people
> keep saying that there's supposed to be a
> /usr/local/libexec/courier-imap/authlib/authvchkpw file or something, I
> don't have that, but authentication works for AWHILE. Then it takes a dump.
>
> Anyone have any suggestions? :(
>
> Taylor
>
