NEthserver 8 supports, Multiple Ldap Account providers, per Host/Node.
During creation of the first, domain on the MAil server, the system asks, which user account to be used, in this case, the first configured ldap domain account is used
WHen creating Subsequent Domains, on the Node, the system assumes, you want to make use of the predefined, or pre-configured ldap account.
What if these users are different, fromm the first one, and i would liek to make use of a seprate user domain for this/ Ldap provder.
@davidep How hard or complex is it from an engineering perspective, to Impelment NS8, so that, each Domain created, could either make use of the existing Ldap account provider, or provide a choice for th suer to chose the Ldap Account they want to Use. considering, already mutliple ldpa accounts are provided for.
I think there might be some confusion in the original question, so let me clarify how this actually works.
The Mail module can only be installed once per node, because it binds to TCP port 25 (and the other standard mail ports), so there’s no such thing as “subsequent domains created on the same node” in the sense of multiple Mail app instances. A single Mail instance binds to exactly one user/account domain (one LDAP account provider). Multiple accepted mail domains (e.g. example.com, example.org) can be configured within that single Mail instance, but they all resolve users through that one bound account provider - they are domain aliases, not separate user realms.
As discussed in other threads, multi-tenancy at the Mail module level (i.e. a single Mail instance serving multiple independent LDAP providers) is not something we plan to implement.
If you need different mail domains tied to different LDAP account providers, that’s already possible today - just deploy a separate Mail module instance on a separate node for each LDAP provider you need to serve. NS8 already supports multiple LDAP account providers across nodes, so this scenario is covered by the existing architecture; it just requires one node (and one Mail instance) per account provider, not multiple domains sharing a single Mail instance.
during creation of the domain, the system does ask for source of users in this case a ldap useracount is chosen.
at this exact juncture, how about ability to choose a different ldap. on the same mail server, on the same node, nod different or multiple nodes.
the wiring already exists. and this is not like multi tenancy, where a different mail server, like in postal is handled etc. its just separation without aliases.
In the email client, make sure that the login name and email address are different.
The login name is therefore either
user1_surname
or
domain2_user1_surname
The use of different email domains is therefore configured only in Mail.app, where the email addresses to be set up point to the respective user in AD as the target.