I had a similar problem under Solaris 7.
I got it to work by changing AUTHMODULES="authuserdb authshadow"
and using local user IDs.
(If you don't shadow your passwords, replace authshadow with authpwd.)
Since I don't use LDAP or PAM, I just left it at that.
One of my friends told me that the authpam module in Solaris (which appears
before authshadow and authpwd in the default AUTHMODULES) is incompatible
with the way Courier uses it, and confuses the Courier authentication
library.
If you run a network user database, then you'll need to dig further. But
see if it works with the above, first, to avoid chasing a wrong lead.
William
Matt Simonsen wrote:
I have just setup a Qmail server on my own using a RedHat 6.2 system. I
have 2 virtual domains setup through the VPopMail add-on from Inter7.
I then compiled Courier-Imap, it is using the default AUTHMODULES. What
is the best way to go about figuring out where my problem is? I have
checked the logs, the only helpful thing (as I understand them) is from
the maillog which shows:
Mar 2 01:53:46 eunomia imaplogin: Connection,
ip=[::ffff:24.177.136.195]
Mar 2 01:53:53 eunomia imaplogin: LOGIN FAILED,
ip=[::ffff:24.177.136.195]
Mar 2 01:54:01 eunomia imaplogin: LOGIN FAILED,
ip=[::ffff:24.177.136.195]
Mar 2 01:54:01 eunomia imaplogin: LOGOUT, ip=[::ffff:24.177.136.195]
IMAP is running on the server, I just can't figure out where the problem
is. Any suggestions would be greatly appreciated, if you need any more
info or details, let me know.
3 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Problems Authenti...
