search for: insecure_setuid

I'm experimenting with checkpassword as an auth method for usedb and passdb (http://wiki2.dovecot.org/AuthDatabase/CheckPassword). I've set up the userdb and passdb *exactly* as the wiki suggests as the "standard way": passdb { driver = checkpassword args = /user/util/bin/checkpassword } userdb { driver = prefetch } I've created a checkpassword program that does

...this thread, I'm trying to get checkpassword to work. I have confirmed that it is setting the environment variables as described in (http://wiki2.dovecot.org/AuthDatabase/CheckPassword). My debug output of env variables sent to checkpassword-reply: $USER=mark userdb_uid=3000026 userdb_gid=100 INSECURE_SETUID=1 EXTRA=userdb_uid userdb_gid I have confirmed that my checkpassword program returns 0 authenticating the user with the AD: fork pid = 4239, ntlm_auth status: 0 The pid listed above is the pid of the forked /usr/local/libexec/dovecot/checkpassword-reply program. For testing purposes, I've r...

...XXX): Error: sync: /usr/local/var/run/dovecot/auth-userdb: Configured passdbs don't support crentials lookups (to see if user is proxied, because doveadm_port is set) I have been hunting through the doc for the last hours and I don't find what to change. I found something about adding set INSECURE_SETUID=1 export INSECUURE_SETUID before checkpassword-reply launch, but it does not change anything... Btw my two server have use the users uid from the ldap, but don't allow user login on the servers where only admin can log in. Does somebody has an idea where to dig ? f.g.