I have been having some issues, on the same. Here is what I have so far:
Host:
You can use the IP Address of your AD/LDAP server, with some issues, or FQDN requires that you’ve setup the docker container to point to the shared DNS service of your network (not the internal docker one). If you’re not on docker, just make sure DNS is setup to resolve the FQDN (host.sumdomain.net for ex.). Use the docker-compose.yml file to add an entry above the 10 existing DNS settings “- 1.1.1.1”
Port:
636 for secure connection to AD (LDAPS://) or 389 for unsecured (LDAP://)
Use SSL:
enable it (slide right) if you chose 636 for the port value, or disable it (slide left) if you chose 389.
Use TLS:
This should be disabled if you are using SSL OR set port 389, enabled if you are using port 636,
Base DN:
This is the DN of your (AD/LDAP) domain; where the query should begin looking for your accounts (ex: OU=myusers,DC=mydom,DC=com).
Filter:
AD/LDAP objects must match this filter TRUE to be considered, for example: (&(objectCategory=person))
Attribute Field:
Bind DN:
This is your distinguished name, for the account that mailcow will use to access your domain; for example: CN=myserviceaccount,OU=users,DC=mydomain,DC=com
Bind Password:
Password to the account you specified in the Bind DN field.
Attribute Mapping:
I don’t know if it’s right but I extended my AD schema of the user class property, with an attribute called “mailcowTemplate”. Set the value to my template, which is default.
Sync settings, you can probably figure out.
I hope this helps someone, somewhere and I hope someone helps me figure out the one I can’t seem to get!
