Version 5.1 |
||||||||||||||||||||||||||||||||
|
|
Domains are the CommuniGate Pro objects that contain other objects: Accounts, Mailing Lists, Groups, Aliases and Forwarders. Each Domain has a domain name (client.com, www.company1.com, etc.):
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: they 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.
Each Domain has its own, independent set of Objects: Accounts, Groups, Forwarders, Aliases, Mailing Lists. Each Object should have a name that is unique within the Domain. Different Objects in different Domains can have the same names.
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.
Use the WebAdmin Interface to view Domain Objects.
Open the Users realm, and follow the link for the selected Domain.
You should have the Can Modify All Domains And Accounts access right to open the Users realm.
If you are a Domain Administrator, then the list of Objects in your Domain appears on the main Domain Administration page.
To select Objects by name, enter a string into the Filter field, and click the Display button: only the Objects with names containing the specified string will be displayed.
The pop-up menu allows you to limit the number of Objects to be displayed.
The checkbox options specify the type of Objects you want to display: Account, Groups, Forwarders, Aliases. The information will include the selected and total number of those Objects in the Domain.
Each line in the list contains an Object name and its type.An Account is the basic service unit: every user served with a CommuniGate Pro Server should have an Account in one of the Server Domains.
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.
Messages directed to an Account address are delivered to the Account using the Local Delivery module.
Signals directed to an Account address are delivered using the Signal component.
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 File Storage.
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.
CommuniGate Pro Domains can contain Groups. Groups are essentially lists of account names and/or other groups and sending a message to a group results in sending it to all group members.
See the Groups section for more information about CommuniGate Pro groups.
CommuniGate Pro Domains can contain Forwarders. Each forwarder has a name and contains an E-mail address for redirection. If mail is sent to name@domain.com where name is a forwarder object in the domain.com CommuniGate Pro domain, then mail is re-routed to the E-mail address specified in that forwarder object.
Group and Forwarder Objects are different:See the Forwarders section for more information about CommuniGate Pro Forwarders.
CommuniGate Pro Domains can contain Mailing Lists. Each Mailing Lists has a name and it always belongs to some account in the same domain - the Mailing List owner.
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.
A Mailbox is the basic storage unit: messages sent to accounts are stored in account mailboxes. Messages can be read from mailboxes, they can be marked with various flags, they can be copied to other mailboxes, and they can be removed from mailboxes.
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.
An Account Alias is an alternative name assigned to a CommuniGate Pro Account. Each Account can have zero, one, or several Account Aliases.
For example, the Account j.smith in the domain2.com Domain can have aliases smith and jsmith. Mail sent to the smith@domain2.com address will be stored in the j.smith Account, and attempts to login as jsmith@domain2.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.