Allow for proper use with remote LDAP servers

Issue #121 wontfix
Izzy
created an issue

I am currently trying to use iRedMail servers with remote LDAP servers where mail addresses are saved with the users, so in the subtree of "dc=example,dc=org", rather than in iRedMails "o=domains,dc=example,dc=org". This is easily possible with a few lines patched in iRedAdmin (Pro) and service configs like dovecot or postfix and could just be asked when installing iRedMail with LDAP backend.

With the current iRedMail it is of course possible to use an existing LDAP server as a database but it would defeat the purpose of having a central management when you have to save every users information in two different places(so o=domains and the general subtree of your domain)

I could provide a crude patch for iRedAdmin Pro LDAP if that helps, not so much for the installation routine though.

Comments (3)

  1. Zhang Huangbin repo owner

    I could provide a crude patch for iRedAdmin Pro LDAP if that helps, not so much for the installation routine though.

    A patch or pull request is always welcome. :)

  2. Zhang Huangbin repo owner

    It's not just the base dn (o=domains,dc=xx,dc=xx vs dc=xx,dc=xx), iRedMail uses hard-coded LDAP tree like this:

    dc=xx,dc=xx
        |- o=domains
            |- domainName=example.com
                |- ou=Aliases
                |- ou=Groups
                |- ou=Users
                    |- mail=user@example.com
    

    Beside the base dn, i believe you have other differences than default iRedMail LDAP tree, we need to change all its child objects as well.

    No other users requested this change till now, so i have no plan to implement this in iRedAdmin-Pro-LDAP.

  3. Log in to comment