Hi, everyone! I just subscribed to the list, so if this is a known issue with a documented solution, please accept my apologies and point me in the right direction.

I spent the weekend installing qmail, vpopmail, qmailadmin, autorespond, ezmlm, sqwebmail and Courier IMAP on a server which is to replace a failing Exchange server. Versions are as follows:

qmail 1.03 (w/AOL DNS patch applied) vpopmail 5.2 qmailadmin 1.0.2 autorespond 2.0.2 ezmlm .53 sqwebmail 3.3.3 Courier IMAP 1.4.4

Everything is functioning as expected for the exception of Courier IMAP. Here's what's happening.

Currently, I have two test accounts set up, danny@ and rachel@. Once rachel@ authenticates for IMAP, danny@ is no longer able to. danny@ can authenticate just fine until rachel@ authenticates once. After that, I must restart Courier IMAP's authdaemond for danny@ to authenticate again and the cycle repeats.

Note that this only works that one way. At no time has rachel@ ever been denied after danny@ logged in.

On one occurrence, danny@ was allowed to connect and retrieve a list of folders even though rachel@ had already authenticated and was still actively connected. However, that was it. Attempting to browse the folders returned an error.

The IMAP client being used for these tests is Pegasus Mail for Windows, version 4.01.

Note that I also have sqwebmail installed, which also requires an authdaemond process. I recall reading in the Courier IMAP docs that only one authdaemond process may be used concurrently. What I'm not clear on is whether this means globally or just for each service, IE: IMAP, sqwebmail, etc... Currently, I have two authdaemond configs running, one each for IMAP and sqwebmail, both configured for authvchkpw only:

authmodulelist="authvchkpw"

I have made two other changes to the authdaemonrc file. They are as follows:

daemons=3 version="authdaemond.plain"

This is a very low volume mail server(less than 20 users), so I didn't think 5 daemons were necessary. And, this issue exists both with authdaemond.ldap and authdaemond.plain. I switched to .plain to see if that resolved the issue. It did not.

Sqwebmail does not appear to be losing it's authentication as Courier IMAP is. At least, not consistently. Once, yesterday, when I first discovered that Courier IMAP was no authenticating danny@, I tried logging in via sqwebmail and was denied. After restarting sqwebmail's authdaemond, I was able to authenticate via sqwebmail. I was very tired and frustrated, so it could have simple been a mistyped password. I have not been able to reproduce that today. Even as Courier IMAP denies danny@ authentication, sqwebmail functions flawlessly.

I doubt that I've provided enough troubleshooting data here. But, I really don't know where to start. Courier IMAP doesn't appear to do much in the way of logging. At least, not that I've found.

Is there something I've overlooked here? Or is this a possible bug in Courier IMAP? Could Pegasus be triggering this somehow?

Any suggestions?

If there's anything I can do to provide more useful data, please let me know.