Hi, my dovecot installation dovecot-2.0.9-19.el6_7.2.x86_64 can't authenticate using winbind from 4.4.3, but it can with winbind from 4.4.2. 4.4.3: May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth): getting password (0x00000010) May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth): pam_get_item returned a password May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth): internal module error (retval = PAM_AUTHINFO_UNAVAIL(9), user = 'john') May 5 22:11:14 sambaserver auth: pam_winbind(dovecot:auth): getting password (0x00000000) May 5 22:11:14 sambaserver auth: pam_winbind(dovecot:auth): internal module error (retval = PAM_AUTHINFO_UNAVAIL(9), user = 'john') May 5 22:11:14 sambaserver auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=gerbenr rhost=213.125.187.194 user=john 4.4.2: May 5 22:18:19 sambaserver auth: pam_winbind(dovecot:auth): getting password (0x00000000) May 5 22:18:19 sambaserver auth: pam_winbind(dovecot:auth): user 'john' granted access May 5 22:18:19 sambaserver auth: pam_winbind(dovecot:account): user 'DOMAIN\john' granted access I upgraded from 4.4.2 to 4.4.3 by doing a fresh compile with the ./configure settings from 4.4.2, then stopping samba, then "make install" and starting samba. Then I got the problems with dovecot (no problems with ssh). I reverted back by stopping samba, doing a "make install" in the 4.4.2 source dir, and starting samba again, and dovecot was OK again. any ideas? Is this a bug? In samba or dovecot? thanks
On 05/05/2016 04:26 PM, Gerben Roest wrote:> Hi, > > my dovecot installation dovecot-2.0.9-19.el6_7.2.x86_64 can't > authenticate using winbind from 4.4.3, but it can with winbind from 4.4.2. > > 4.4.3: > > May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth): getting > password (0x00000010) > May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth): > pam_get_item returned a password > May 5 22:11:07 sambaserver auth: pam_winbind(dovecot:auth): internal > module error (retval = PAM_AUTHINFO_UNAVAIL(9), user = 'john') > May 5 22:11:14 sambaserver auth: pam_winbind(dovecot:auth): getting > password (0x00000000) > May 5 22:11:14 sambaserver auth: pam_winbind(dovecot:auth): internal > module error (retval = PAM_AUTHINFO_UNAVAIL(9), user = 'john') > May 5 22:11:14 sambaserver auth: pam_unix(dovecot:auth): authentication > failure; logname= uid=0 euid=0 tty=dovecot ruser=gerbenr > rhost=213.125.187.194 user=john > > > 4.4.2: > > May 5 22:18:19 sambaserver auth: pam_winbind(dovecot:auth): getting > password (0x00000000) > May 5 22:18:19 sambaserver auth: pam_winbind(dovecot:auth): user 'john' > granted access > May 5 22:18:19 sambaserver auth: pam_winbind(dovecot:account): user > 'DOMAIN\john' granted access > > I upgraded from 4.4.2 to 4.4.3 by doing a fresh compile with the > ./configure settings from 4.4.2, then stopping samba, then "make > install" and starting samba. Then I got the problems with dovecot (no > problems with ssh). > > I reverted back by stopping samba, doing a "make install" in the 4.4.2 > source dir, and starting samba again, and dovecot was OK again. > > any ideas? Is this a bug? In samba or dovecot? > > thanks >Can you upgrade Dovecot to the latest version, 2.2.24? That might resolve your problems.
Reasonably Related Threads
- primary group gets set to 100 on Samba AD server after a while
- primary group gets set to 100 on Samba AD server after a while
- primary group gets set to 100 on Samba AD server after a while [SOLVED]
- Samba 4.4.2 as AD server: clients OK but server fails "wbinfo -K"
- Samba 3, Windows 7 and printer drivers