Re: Working with Active Directory on Windows Server 2012 R2

I’ve fixed the issue by using a slightly different configuration. Particularly the problem was due to mistaking %u (user@domain) vs %n (just user). Here are the configuration files for anyone looking to get it working with Active Directory on 2012 R2 on Dovecot 2.2.9 (or similar, whatever comes

Re: Working with Active Directory on Windows Server 2012 R2

I’ve removed the dn / dnpass. When attempting with new user: $ cat /var/log/dovecot-info.log Nov 27 00:09:29 imap-login: Info: Internal login failure (pid=5553 id=1) (internal failure, 1 successful auths): user=, method=PLAIN, rip=10.211.55.29, lip=10.211.55.33, mpid=5558, TLS, session= Nov 27

Re: Working with Active Directory on Windows Server 2012 R2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 26 Nov 2014, Aaron Jenkins wrote: I’ve attempted the user Mail with the same password with the same result (binding as my own user was a last-ditch attempt). OK, what about the: As I understand auth_bind_userdn, y

Re: Working with Active Directory on Windows Server 2012 R2

I’ve attempted the user Mail with the same password with the same result (binding as my own user was a last-ditch attempt). aaron@aaron-Parallels-Virtual-Platform:/etc/sssd$ ldapsearch -x -H ldap://dc1.ad.automaton.uk -D CN=aaron.jenkins,CN=users,DC=ad,DC=automaton,DC=uk -W - -b CN=aaron.jenk

Re: Working with Active Directory on Windows Server 2012 R2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 25 Nov 2014, Aaron Jenkins wrote: I’m having issues getting Dovecot to work with AD on 2012 R2 in a test environment. … Nov 19 09:22:23 auth: Debug: auth client connected (pid=10345) Nov 19 09:22:23 auth: Debug: client in: AUTH 1 PLAIN serv

Working with Active Directory on Windows Server 2012 R2

Hi all, I’m having issues getting Dovecot to work with AD on 2012 R2 in a test environment. Background: AD is running on dc1.ad.automaton.uk, the domain is ad.automaton.uk. The DNS server is running on ad.automaton.uk