DEBUG_LOGIN=2 is set. But there are no logs.The only courier messages I get are the startup notices in /var/log/messages. I've even done a lsof on the logger, and it doesn't seem to have any log files open. That's a good part of why I am confused.
On Wed, Aug 12, 2020 at 4:56 AM Sam Varshavchik <mr...@courier-mta.com> wrote: > Dan Egli writes: > > > « HTML content follows » > > > > > > I am needing some help here. I downloaded the courier source and used > CentOS > > 7's rpmbuild to make rpms to install. After everything is installed I > tried > > to test it. But it always says login failed. I'm using a mysql database > for > > username/password storage. The courier system should be able to login to > the > > db no problem, since I tested it on the command line and was able to > login to > > the correct db using the credentials I assigned. But whenever I try to > > authtest or login directly, it fails. The only message I get is login > failed. > > I've checked the log files and cannot find anything. In fact, courier > only > > seems to be logging it's startups. > > > > any suggestions? I'm at a loss. > > Setting DEBUG_LOGIN=2 in authdaemonrc (and restarting courier-authlib) > results in logging of all SQL. Then you can use authtest, get the SQL > that > was executed, and try it for yourself, to see what works and what doesn't. > > _______________________________________________ > Courier-imap mailing list > Courier-imap@lists.sourceforge.net > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap >
_______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap