Available as of 1.5.1 and expected to evolve somewhat in following releases. There is a vast range of LDAP schemas in use, PowerMail strives to be able to talk to most of those with only configuration file tuning.
To verify passwords, PowerPOP tries to bind to a record, leaving the actual password check to the LDAP server. Based on the domain specified by the user, a base is chosen to bind with.
![]() | TODO: get quotas hooked up |
Settings:
LDAP host(s) to connect to. Separate by spaces. Defaults to 127.0.0.1.
A space separated list of domain:base pairs. For example, "ds9a.nl:ou=People,dc=ds9a,dc=nl" would indicate that the mailboxes in the 'ds9a.nl' domain are to be searched for in ou=People,dc=ds9a,dc=nl.
Multiple domains can be specified, as well as a default map: "ds9a.nl:ou=People,dc=ds9a,dc=nl ou=People,dc=bigisp". This will cause all other domains to be looked up with ou=People,dc=bigisp as search base.
Attribute to search on. With the map above, a message for "ahu@ds9a.nl" with ldap-search-attribute=uid leads to a search on (uid=ahu) within "ou=People,dc=ds9a,dc=nl". PowerDNS does 'scope=subtree' searches.
If non-empty, this attribute is checked for a forwarding email address for this mailbox. The account can however still log in to retrieve remaining messages.
In addition, PowerMail has support for alternate addresses, as used with qmailldap. For this to work, three additional parameters are provided:
Attribute containing the full alternate addresses.
How to derive the mailbox name from the record. This takes the value in the ldap-search-attribute content as local-part and adds this domain to it.
Base to use when searching for the alternate attribute.