The CommuniGate Pro Server software implements Directory-based Domains. Directory-based Domains and all their Accounts keep all their settings in the Directory - there is no .settings files for those Domains and Accounts.
For each Directory-based Domain a Directory record of the CommuniGateDirectoryDomain objectClass is created. This record stores all Domain Settings. DNs for Directory-based Domains are built in the same way they are built for Regular Domain records.
For each account in a Directory-based Domain a Directory record of the CommuniGateAccount objectClass is created. This record stores all Account Settings (including the Custom Settings). DNs for accounts in the Directory-based Domains are built in the same way they are built for Regular Domain Account records.
Directory records for Directory-based Domain Accounts must contain the storageLocation attribute. This attribute specifies the location of the Account file directory (for the multi-mailbox accounts) or the location of the Account INBOX (for single-mailbox accounts). The location is specified as a file path relative to the base directory of the CommuniGate Pro Server hosting this Account.
If a CommuniGate Pro server has to open an Account in a Directory-based Domain, and the Account storageLocation attribute starts with the asterisk (*) symbol, the CommuniGate Pro Server creates the Account file directory (for multi-mailbox Accounts) and other required Account files and file directories.
Directory records are created for aliases of Directory-based Domain Accounts.
Alias records have the same DNs as Accounts (uid=aliasname,domain DN).
Alias records have the standard alias objectClass, and their aliasedObjectName attribute specifies the DN of the original account record.
The following diagram illustrates how the LDAP AddRecord operation can be used to create an Account in the Directory-based Domain:
In this example:
Since the Account in the Directory-based Domains do not store their settings in the CommuniGate Pro data files, the settings are retrieved from the account Directory record every time an account has to be opened. The following diagram illustrates this procedure