In many cases, a mail domain should not have a separate set of user accounts, but should rather be a domain name alias for an already existing CommuniGate Pro Domain. You may also want to serve some mail domains using account mapping and/or Unified Domain-Wide Accounts. In all these cases, you do not have to create a new CommuniGate Pro Domain to serve a mail domain.
See the Mapping section for the details.
When a client application (a mailer) connects to your CommuniGate Pro Server, and specifies an account name, the Server has to detect in which Domain to look for that Account.
You can use multiple domains if:
To display the list of all Domains served with your server, use a Web browser and enter the Domains section. You should be connected as the Postmaster or any other user with the Can Modify All Accounts and Domains access rights.
To select domains by name, type a string into the Filter field, and click the Display button: only the domains with names containing the specified string will be displayed.
Each entry in the domain list contains the Domain name, the assigned network address (if any), and the number of Accounts in the Domain. If the Domain is a shared Domain served by a Dynamic Cluster, the Domain name has the [+] prefix. If the Domain is a Directory-based Domain, its name is displayed with the [D] prefix.
A list entry also displays the number of currently opened domain accounts, the total number of times domain accounts have been opened (since the Server last restart), and the last time any domain account was opened.
Select the Show Aliases option to include domain aliases into the list. Each domain alias list element contains the link to its "real" domain account list and settings pages.
Click a domain name to view the accounts in that domain.
Click the word Settings in the last column to view and update the domain Settings.
Type a new domain name into the field on the right side of the Create Domain button.
Click the Create Domain button. When a new domain is created, its name appears in the Domain List.
If a server is a member of a Dynamic Cluster, the additional Create Shared Domain button appears. Click that button to create a domain that will be served by all members of the Cluster. The domain created using the Create Domain button are created as "local" domains and are served by this server only.
Main domain and all Secondary Domains have domain-level settings.
To open the Domain Settings page in your browser, either click the Domain Settings link in the Domains List, or click the Domain Settings link on the domain Accounts List page.
The Account Log option allows you to specify how the account-level operations (account open/close, password verifications, mailbox creating/removing, size updates, etc.) are recorded. Log records created for account-related events have the ACCOUNT tag.
The Mailbox Log option allows you to specify how the mailbox-level operations (message storing/removing, message status updating, etc.) are recorded. Log records created for mailbox-related events have the MAILBOX tag.
Most of Domain Settigs can be set to the Default value. In this case the actual setting value is taken from the global, Server-wide Default Domain Settings.
When the Domain Settings are modified, click the Update button. The page should appear again, displaying the Updated marker.
You can click the Accounts link to switch to the domain Account List.
You should read this chapter only if you plan to support multihoming, if your system is behind a firewall, or if you have a non-standard Domain Name System setup.
When the Server starts, it detects its own network address(es). Your Server system is "multihomed" if it has more than one network (IP) address.
If the Server system has several IP addresses, some of them can be assigned (dedicated) to secondary domains. Accounts in such domains can be accessed using any POP and IMAP mailer without explicitly specifying the full account name.
The Assigned IP Addresses option allows you to assign network addresses to the main and secondary domains.
For each Domain in the Domain List, the assigned network (IP) addresses are displayed. This can be used to check the DNS and Server setup for systems with multihoming.
Because of setup errors or due to a non-standard network and DNS setup, the Server's own IP address(es) may be left unassigned to any of the Server domains. Open the General Settings page to see the list of the Server own IP addresses. The unassigned addresses are marked in red.
When a client mailer connects to the Server via an unassigned address and the full account name is not specified, the Server does not allow the user to log in.
Each Domain has a set of settings that specify which CommuniGate Pro services can be used with the Domain Accounts:
Services can also be disabled for individual Domain Accounts.
A service is available for an Account only if that service is enabled for the Account itself AND
for the Account Domain. Disabling a service in the Domain Settings disables that service
for all Domain Accounts.
Note: This is different from disabling a service in the Domain Default Account Settings: disabling a service in the Default Account Settings disables that service only for those Domain Accounts that have the Enabled Services option set to default.
The System Administrator can specify some limits on the resources available to the Domain users.
A Domain Administrator can see, but cannot modify these limits.
Each CommuniGate Pro domain can have aliases (alternative names). If the domain client.dom has the mail.client.dom and www.client.dom aliases, mail directed to email@example.com and to firstname.lastname@example.org will be routed to the email@example.com account. Also, to access the firstname.lastname@example.org account via POP, IMAP, and other mailer applications the account names email@example.com and firstname.lastname@example.org can be specified in the mailer settings.
This is especially useful for WebUser clients. Users specify the domain name in their browser URLs, and users of the client.dom domain tend to use www.client.dom in the browser URLs. You may want to register the www.client.dom domain with the DNS, assigning it the same IP address as the address assigned to the client.dom domain, and then you should create the www.client.dom alias for the client.dom domain.
You can modify existing aliases, add an alias by typing a new name in the empty field, and remove an alias by deleting it from its field. Use the Update button to update the list of domain aliases.
The Domain Aliases are stored in the DomainAliases database located in the Settings directory inside the CommuniGate Pro base directory.
This panel is not displayed for Directory-Based Domains, since those domains are always completely integrated with the Directory.
See the Directory Integration section for the details.
The administrator can enable the special virtual list (address) "all" that can be used to send messages to all Accounts created in this Domain.
Messages sent to the <all@domainname> address are stored directly in the Account INBOX mailboxes, bypassing any Account Rules.
Messages sent to the <all@domainname> address are not stored in the Accounts that have the Accept Mail to All setting disabled.
Mail access to the <all@domainname> address can be restricted.
Messages to <all@domainname> can be sent to all Forwarder addresses, too:
If the administrator has enabled mail distribution to all accounts in the main domain, a message can be sent to all accounts in all domains.
To send a message to all accounts in all server domains, it should be sent to the alldomains@main_domain_name address.
For each domain, the message source is checked and the message is distributed to the domain accounts only if it passes that domain "Mail to All" distribution checks.
The Server checks that an account with the specified name does not exist and creates a new account. The Server uses the Account Template settings for the newly created account, overriding its Password and Real Name settings with the data specified by the new user.
The available options include:
The CommuniGate Pro allows you to create Accounts with external INBOX mailboxes. These mailboxes are stored not inside the CommuniGate base directory, but in the system file directory known to the legacy mailer applications.
If you have to support Local Mailer compatibility for all or some accounts in a domain, you should specify the External INBOX settings:
See the Sharing section for the details.
If this field is not empty, the Domain Administrator Accounts created in this Domain and the Domain Administrator Accounts created in the specified Domain can be used to administer this Domain.
See the System Administrator section for more details.
If there is no other domain with the same name as the specified new domain name, the domain is renamed and its Domain Settings page should reappear on the screen under the new name.
You cannot rename a domain when any of its accounts is in use.
If you want to remove a Secondary Domain, open its Domain Settings page with a Web browser, and click the Remove Domain button. The confirmation page should appear. If the Empty Domains Only option is selected, a Secondary Domain is removed only if there are no accounts in it. Otherwise, all Domain Accounts are permanently removed, too.
If you confirm the action, the selected domain, its settings, and all its accounts will be permanently removed from the Server disks.
You cannot remove a domain when any of its accounts is in use.
The Default Domain Settings page resembles a regular Domain Settings page.
A Dynamic Cluster installation maintains separate server-wide Default Domain settings for all non-Shared (Local) Domains, and cluster-wide Default Domain settings for all Shared Domains. In the Cluster environment, the Default Domain Settings page displays links that allow you to switch between the Server-wide and Cluster-wide Default Settings.
A Domain can have its own set of enabled Authentication methods. See the Security section for more details.
A Domain can have PKI settings (Private Keys and Certificates) enabling
secure communications (TLS, Certiciate Authentication, S/MIME) with that Domain.
Use the Security link on the Domain Settings page to open the Domain Security settings.
See the PKI section for more details.
A Domain can have Kerberos keys enabling secure single signon for that Domain.
Use the Security link on the Domain Settings page to open the Domain Security settings.
See the Security section for more details.
The secondary Domains data is stored in the Domains file directory inside the base directory. For each secondary Domain, a directory with the Domain name is created in the Domains directory. All shared Domains in a Dynamic Cluster and stored as subdirectories of the SharedDomains directory.
If your server or cluster serves many (more than 3,000) Domains, you may want to create additional Domain Subdirectories inside the Domains and/or SharedDomains directory.
Each Domain directory contains data for all Domain Accounts.
When a domain contains many Accounts, Account Subdirectories inside the Domain directory can be used.
When a CommuniGate Pro system serves many Domains (more than 3,000), you may want to place Domain files directories into several subdirectories:
Subdirectories can be nested.
Note: When the CommuniGate Pro Server starts, it scans the Domains directory and all its .sub subdirectories, and it collects the names and file paths of all Domains it finds there. This feature allows the administrator to change the foldering method (see below) without stopping the Server and without relocating already created Domains. It also allows the system administrator to move Domains between subdirectories at any time when the CommuniGate Pro Server is stopped.
When a new Domain is being created (or when an existing Domain is being renamed), the Server composes a name for the subdirectory in which the Domain files should be created. The Domain Storage panel contains the settings that control how a subdirectory name is composed. Open the Domains page of the WebAdmin Interface, and follow the Domain Defaults link to open the page that contains the Domain Storage panel:
Note: if you cannot store all Domains on one disk volume, you can copy some xx.sub directories to other volumes, and replace them with symbolic links.
Account subdirectories are directories inside the Domain directory. A subdirectory name has the .sub file path extension (suffix).
Subdirectories can be nested.
Note: When the CommuniGate Pro Server starts, it scans all domain directories and all their subdirectories, and it collects the names of all domain Accounts. This feature allows the system administrator to move accounts between subdirectories at any time when the server is stopped. It also allows you to change the foldering method (see below) without stopping the server and without relocating already created accounts.
For each Account, the CommuniGate Pro Server remembers the name of the subdirectory that contains the account files.
When a new Account is being created (or when an existing Account is being renamed), the Server composes a name for the subdirectory in which the Account files should be created.
Note: many other mail systems process large Domains with account subdirectories, too. Every time an account is to be opened, those systems form the account subdirectory name using some built-in method. As a result, the built-in method cannot be changed "on the fly", and accounts cannot be moved between subdirectories. The CommuniGate Pro Server uses its subdirectory name forming methods only when a new Account is being created or when an Account is being renamed, and it always remembers in which subdirectory every Account is located. The Server does not have to form the subdirectory name every time an Account is to be opened. As a result, the CommuniGate Pro domain "foldering" methods can be changed at any moment, and the Accounts can be moved between the subdirectories when the server is not running.
Note: if you cannot store all Domain Accounts on one disk volume, you can copy some xx.sub directories to other volumes, and replace them with symbolic links.
Note: if you have stopped the Server and manually moved/removed some Domain Account directories, delete the Index.data file from the Domain directory before you start the Server again.
Note: if you want to keep only symbolic links in the Domain file directory, you can create the Index subdirectory inside the Domain directory (or an Index symbolic link to some other directory). If this subdirectory exists, the Server stores the Index.data file inside that subdirectory rather than in the Domain file directory itself.