While each CommuniGate Pro Domain has its domain name, it is not necessary to create a separate CommuniGate Pro Domain for each domain name you want to serve. CommuniGate Pro Domains can have domain aliases, that allow you to assign several names to the same CommuniGate Pro Domain. For example, the CommuniGate Pro Domain company.com may have a domain alias mail.company.com. In this case all references to the domain name mail.company.com will be processed as references to the company.com CommuniGate Pro Domain.
There is a special CommuniGate Pro Domain, called the Main Domain. Other CommuniGate Pro Domains are called secondary domains. The Main Domain is created as soon as the Server is installed, and its name is specified in the General Settings. If your Server should serve only one Domain, the Main Domain is all you need and there is no need to create secondary domains. The Main Domain name is used as the Server Name.
Each CommuniGate Pro Domain has its own settings and a set of Domain Objects.
See the Domains section for more information about CommuniGate Pro Domains.
Object names are case-insensitive. Object names can contain latin letters, digits, the underscore (_), the minus (-), and the point (.) symbols. The point symbol cannot be used as the first or the last symbol of an Object name.
Object names should not contain more than 128 symbols.
Each account is protected with a password, so only the account owner (and, optionally, system and domain administrators) can have unrestricted access to account data.
When the CommuniGate Pro Server is installed, the postmaster account is automatically created in the main domain. The Master (unlimited) access right is granted to that account.
Accounts are created inside CommuniGate Pro domains.
Each CommuniGate Pro domain has its own set of accounts. Accounts should have unique names within their domain, but two accounts in different domains can have the same name.
Account E-mail address is accountname@domainname address where accountname is a name of a CommuniGate Pro account, and domainname is the name of the CommuniGate Pro domain in which this account is created. Messages directed to this account address are delivered to the account using the Local Delivery module.
An Account may have several names (for example, john.smith and jsmith). An administrator can create account aliases to assign several names to one Account.
Each CommuniGate Pro Account has its own settings and a set of Mailboxes.
Each CommuniGate Pro Account has its own Personal File Site.
Accounts can also store additional information and data. See the Account Data section for the details.
See the Accounts section for more information about CommuniGate Pro Accounts.
See the Groups section for more information about CommuniGate Pro groups.
Group and Forwarder Objects are different:
See the Forwarders section for more information about CommuniGate Pro Forwarders.
Mailing list contains a list of subscribers, and it maintains several mailboxes in the list owner account. Those mailboxes are used to store and archive postings, generate digests, store subscription requests and error reports.
Groups and Mailing Lists are different:
See the LIST section for more information about CommuniGate Pro Mailing Lists.
Each account can have one or several mailboxes. The INBOX mailbox is special: it exists in every account, and it is used to store incoming messages. The INBOX mailbox is created automatically when an account is created. A user cannot remove the INBOX mailbox, but a user can rename it. In this case, a new empty INBOX is immediately created.
CommuniGate Pro allows administrators to create single-mailbox accounts. These accounts contain only the INBOX mailbox.
The CommuniGate Pro Server provides access to account mailboxes via POP, IMAP, WebUser Interface and other modules.
CommuniGate Pro mailboxes can have various formats. Administrators and users can select the mailbox format when they create a new mailbox.
See the Mailboxes section for more information about CommuniGate Pro Mailboxes.
For example, the Account j.smith in the domain2.com Domain can have aliases smith and jsmith. Mail sent to the firstname.lastname@example.org address will be stored in the j.smith Account, and attempts to login as email@example.com will open the same j.smith Account.
You can use Forwarders to assign alternative name for Accounts, too. If you create the Forwarder js in the domain2.com Domain, and make it point to the j.smith address, it will work as yet another alias for the j.smith Account.
If you rename the account j.smith into james.smith, all Account Aliases will "move" with it - smith and jsmith will remain the Aliases for the james.smith Account. If you remove the Account, the Account Aliases will be removed, too.
Renaming and removing of Accounts has no effect on the Forwarders: if you rename or remove the j.smith Account, the Forwarder js will continue to point to the j.smith address.
As a result, it is not recommended to use Forwarders where you can use Aliases. Forwarders should be used to create "objects" that redirect mail to other Domains or to other mail servers.
The Account Settings specify the user password and resource limits (maximum mailboxes size, number of files in the Personal File Site, etc.), authentication methods, and other individual options.
It is convenient not to specify the same setting value explicitly for each account, but let all accounts in a domain, or even all accounts on the CommuniGate Pro server use the same setting value that can be modified for all accounts at once. If you specify the default value for an account setting, the system will use the setting value retrieved from the Default Account Settings for the account domain. The domain Default Account Settings can themselves be specified as having the default value, in this case the setting value is retrieved from the global Default Account Settings specified for the entire Server.
Each CommuniGate Pro Domain has individual settings. Settings are specified by the system or domain administrator.
It is convenient not to specify the same setting value explicitly for each domain, but let all domains use the same setting value that can be modified for all domains at once. If you specify the default value for a domain setting, the system will use the setting value retrieved from the Default Domain Settings.
|The global (Server)||Default Account Settings:||Storage Limit = 10Mbytes|
|The company.com||Default Account Settings:||Storage Limit = 30Mbytes|
|The client.com||Default Account Settings:||Storage Limit = default|
When you serve many accounts, you should try to specify most of the setting values as default, so you can easily change those settings for all accounts. If some account should be treated differently, you explicitly specify the required setting value for that account.