Hi, I have dovecot 2.0.beta6 and I'm newbie with dovecot. I try authenticate user via LDAP (MS ActiveDirectory). I have errors in log: mail dovecot: auth: Error: LDAP: binding failed (dn cn=administrator,ou=users,dc=my,dc=domain): Invalid credentials, 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece
This is my dovecot.conf file: protocols = imap disable_plaintext_auth = no listen = * ssl = no auth_mechanisms = plain base_dir = /var/run/dovecot/ mail_location = mbox:/home/vmail/%n/
passdb { driver = ldap args =/etc/dovecot/dovecot-ldap.conf }
userdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf }
And this is my dovecot-ldap.conf: hosts = 192.168.0.19 dn = cn=administrator,ou=users,dc=my,dc=domain dnpass = password base = ou=myuser,dc=my,dc=domain scope = subtree ldap_version = 3 auth_bind = yes auth_bind_userdn = ou=myuser,dc=my,dc=domain
user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u))
Should I have any file in /etc/pam.d ?
Thanks
On Wed, Jan 19, 2011 at 05:27:52PM -0500, Charles Marcus wrote:
On 2011-01-19 5:04 PM, pch0317 wrote:
I have dovecot 2.0.beta6 and I'm newbie with dovecot.
First assignment: upgrade to 2.0.9... why waste time fighting with bugs that are already long fixed?
RHEL6 ships dovecot 2.0-beta6 (2.0-0.10.beta6.20100630.el6), and many sysadmins like to stick with the distro provided packages, so I think we'll see quite a few of these until RHEL6.1 or something hopefully upgrades the package to something newer..
We sysadmins should be proactive about known bugs -- so maybe we should set up test cases for all known bugs fixed since 2.0-beta6, and report these to Red Hat support ? ;-)
-jf
On 2011-01-20 3:31 AM, Jan-Frode Myklebust wrote:
On Wed, Jan 19, 2011 at 05:27:52PM -0500, Charles Marcus wrote:
On 2011-01-19 5:04 PM, pch0317 wrote:
I have dovecot 2.0.beta6 and I'm newbie with dovecot.
First assignment: upgrade to 2.0.9... why waste time fighting with bugs that are already long fixed?
RHEL6 ships dovecot 2.0-beta6 (2.0-0.10.beta6.20100630.el6), and many sysadmins like to stick with the distro provided packages, so I think we'll see quite a few of these until RHEL6.1 or something hopefully upgrades the package to something newer..
There are other repos for getting working stable builds... refusing to do so and sticking with a known buggy pre-release version of critical software is just not a good idea. If my chosen distro put me in that position, then I'd find another distro.
--
Best regards,
Charles
On 20/01/11 13:31, Charles Marcus wrote:
On 2011-01-20 3:31 AM, Jan-Frode Myklebust wrote:
On Wed, Jan 19, 2011 at 05:27:52PM -0500, Charles Marcus wrote:
On 2011-01-19 5:04 PM, pch0317 wrote:
I have dovecot 2.0.beta6 and I'm newbie with dovecot.
First assignment: upgrade to 2.0.9... why waste time fighting with bugs that are already long fixed?
RHEL6 ships dovecot 2.0-beta6 (2.0-0.10.beta6.20100630.el6), and many sysadmins like to stick with the distro provided packages, so I think we'll see quite a few of these until RHEL6.1 or something hopefully upgrades the package to something newer..
There are other repos for getting working stable builds... refusing to do so and sticking with a known buggy pre-release version of critical software is just not a good idea. If my chosen distro put me in that position, then I'd find another distro.
ok, I fix this error.
Instead dn = cn=administrator,ou=users,dc=my,dc=domain should be dn = cn=administrator,cn=users,dc=my,dc=domain
thx
participants (3)
-
Charles Marcus
-
Jan-Frode Myklebust
-
pch0317