On 5/03/2014 16:31, Anders Le Chevalier wrote: > > On 2014-03-04 09:01, Kristian Duus Østergaard wrote: >> On 2014-03-04 06:43, Anders Le Chevalier wrote: >>>>> Yes, I recall that episode. crypt() was returning a null pointer. >>>>> What's happening is that the primary authentication module is not >>>>> one of the system authentication modules. It might be authpam, or >>>>> one of the database or ldap modules. When authentication requests >>>>> fail, this falls through to the next available authentication >>>>> module, authshadow or authpwd, which attempt to use crypt() which >>>>> fails and returns a null pointer. >>>>> >>>>> The easy way to fix this is to simply remove authshadow and authpwd >>>>> from the authmodulelist setting in the authdaemonrc configuration >>>>> file. They're broken, and they'll never work. >>>>> >>> I have disabled all modules except mysql in authdaemonrc. Perhaps this >>> will help. >>> >>> >>> ~A >> Anders are you sure you have modified the correct authdaemonrc ? >> >> I found out that I have a leftover /etc/courier/authdaemonrc the one >> that needs modifying is : >> >> /etc/courier/authlib/authdaemonrc >> >> I have now removed authshadow from my system, and I will let you know if >> it removes the error tomorrow. >> >> Regards >> Kristian >> > Thanks. Yes, I did change the correct file. I have only one module > loaded: authmodulelist="authmysql" > > This is also visible in the mail log when someone is trying to logon. > Note the last two lines: > > > ######################### > > <snip> > Mar 5 06:08:05 e350 authdaemond: authmysqllib: connected. Versions: > header 50170, client 50170, server 50170 > Mar 5 06:08:05 e350 authdaemond: Install of a character set for MySQL: utf8 > Mar 5 06:08:05 e350 authdaemond: SQL query: SELECT id, crypt, clear, > uid, gid, home, maildir, "", name, "" FROM passwd WHERE id = > 'a...@siwnet.net' > Mar 5 06:08:05 e350 authdaemond: zero rows returned > Mar 5 06:08:05 e350 authdaemond: no password available to compare > Mar 5 06:08:05 e350 authdaemond: authmysql: REJECT - try next module > Mar 5 06:08:05 e350 authdaemond: FAIL, all modules rejected > > ######################### It would appear that you don't have a row in the passwd table where id = 'a...@siwnet.net', which therefore means that you can't log in. Possibly asking the obvious, but have you tried running the SELECT query manually?
When I was setting up my custom SQL table, I tested the SELECT query directly within MySQL before applying it in my Courier config. This ensured that I had data to feed in to authdaemond. Regards, Tim Lyth ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
