This is reply text posted at the top - hence the term "top-posting"... ;-)
On Mon October 31 2005 04:12, Robert Samuel White wrote:
This is a follow up to my email. I noticed that the debug settings I made
for authdaemon were not working, so I fixed it, and now, after I try to log
in, I receive the following:
Oct 31 04:58:06 server authdaemond: received auth request, service=pop3,
authtype=login Oct 31 04:58:06 server authdaemond: FAIL, all modules
rejected
This confirms that it is not accepting mysql as an authorization method. I
confirmed all the mysql settings and that the mysql server would grant it
access.
It sounds mysql specific, which I'm not using....
I thought you installed from rpm's?
RC.LOCAL FILE:
[root@server bin]# tail /etc/rc.local
/usr/local/apache2/bin/apachectl start
/usr/sbin/authdaemond start
/usr/lib/courier/sbin/courier start
/usr/lib/courier/sbin/pop3d start
/usr/lib/courier/sbin/imapd start
/usr/lib/courier/sbin/esmtpd start
/usr/lib/courier/sbin/webmaild start
Don't do that - use chkconfig and service...
AND FINALLY, ONE RANT:
The Installation instructions on the website need to be updated! Many of
the paths on that website do not correlate to the paths that were
AUTOMATICALLY placed on my server when doing the RPM install - making it
very difficult for someone like me to know if I need to move things around
to make sure the correct files are read (authdaemonrc, for example.)!
Paths for packages built from source are relative - get used to it. In other
words, generally available doc's, such as on a website, cannot include all
possible "configure" paths given by every sys. admin. - it's simple enough to
think in terms of etc/ bin/ sbin/ etc...
What paths do not correlate? Matching the rpm install might be reasonable,
though, Sam?
jerry
10 messages in net.sourceforge.lists.courier-users[courier-users] Re: Courier Authentic...
