System Administration |
||||||||||||||||||||||||||||||||||||||||||||||||
|
The Server administration pages are divided into four groups (realms). To access a page in any group, a user should be registered with the CommuniGate Pro Server (should have an account on the Server), and the user should be explicitly granted access rights to that section.
Note: If a user is granted the Master access right, that user can access all other sections.
Note: These access rights can be granted to the accounts (users) in the main domain only. Accounts in secondary domains can be granted domain administration rights only.
When a Server is installed for the first time, it creates the postmaster account in the main domain, assigns a random password to that account, and grants the Master access right to the postmaster user.
All CommuniGate Pro Server files - accounts, domains, mailboxes, settings, queues, etc. are stored in one place - in the Server base directory.
When the Server starts, it creates the following objects inside its base directory:
For more information about the Account and Domain files and directories, see the Account Data section.
You can use symbolic links to move some of these directories to other locations (and other disks).
Start configuring the Server by opening the General page in the Settings section.
Note: messages directed to this and only this domain name will be processed as local. If the Main Domain Name is entered as company.com, then messages to abc.company.com will not be processed as local, and if such a message is received, the server will try to deliver it to the abc.company.com computer over the network. If the DNS record for the abc.company.com points to the same Server computer, the mail loop error will be detected, and the message will be rejected.
If your server should process mail for several domains, enter the additional domain names as Mail Domain Aliases (if those domains should be mapped to the main domain), or create additional Secondary Domains.
It's unlikely you will ever meet a problem with the kernel itself.
If you see any problem with the Server, try to troubleshoot which component
could be the cause of it, and change the Log setting of that component
(Router, SMTP, POP, etc.) to get more information.
The kernel records in the System Log are marked with the SYSTEM tag.
You may want to disable this option if you see some exception raised
messages in your CommuniGate Pro Log and/or in the OS system.log or mail.log
and you want the Server to stop when an exception is raised again, and to produce a core dump file,
that can be uploaded to the Stalker ftp site for examination.
Stalker Software would recommend you to disable this option if you are running any beta-version of the
CommuniGate Pro software.
On Unix platforms, you can use the startup script with the stop parameter, or you can get the Server process id from the ProcessID file in the base directory and use the kill command to stop the server.
On the Windows NT platform, you can use the Services control panel to stop and start the CommuniGate Pro server.
You can also use the shutdown CLI API command to stop the server.
When the Server receives a shutdown request, it closes all the connections, commits or rolls back mailbox modifications, and performs other shutdown tasks. Usually these tasks take 1-3 seconds, but sometimes (depending on the OS network subsystem) they can take more time. Always allow the server to shut down completely, and do not interrupt the shutdown process.
The Server places records into the OS log (system.log or mail.log):
A domain administrator can use the WebAdmin interface to access the pages in the Accounts section, but the access is limited to that domain only, and not all domain and account Settings can be modified.
When you grant the domain administrator access right to a user, you will see a list of specific access rights - the internal names of Domain and Account Settings. You should specify which settings the domain administrator can modify. Also, the list of enabling options allows you to grant the domain administrator rights:
The domain administrator can also upload and update the WebUser Interface pages, if you grant the CanCreateWebPages access right to that administrator.
The domain administrator access right can be granted to users in secondary domains by a system administrator that has the Accounts (All Domains and Account Settings) access right.
A Domain administrator can control the domain using the same WebAdmin port (see HTTP module description for the details), or using the Command Line Interface commands.
To modify the Domain WebAdmin interface pages, connect to the server WebAdmin Interface as a Server Administrator, open the Domain Settings page and click the WebAdmin link. The list of WebAdmin files will appear. Click the Accounts link to open the subdirectory containing the files used to compose WebAdmin pages in the "Account" realm:
If the file does not exist in the domain WebAdmin directory, the file from the application directory WebAdmin subdirectory is shown, and the default marker is displayed. If the file exists in the domain WebAdmin directory, that file is shown and a check box is displayed in the Marker field.
To modify some element of the WebAdmin Interface:
If the WebAdmin directory/subdirectory did not contain a custom copy of the uploaded file, you will see the default file marker changing to a checkbox. If a custom version of that file already existed in the WebAdmin directory/subdirectory, the old version is replaced with the uploaded one.
To remove a custom version of a WebAdmin Interface file, select the checkbox on the left of that file name and click the Delete Marked button. If the file with that name exists in the application directory WebAdmin subdirectory, the file name does not disappear from the WebAdmin Interface Editor page, but the name gets the default marker indicating that the default (original) version of the file will be used again.
Note:The Server WebAdmin interface always uses the files located in the WebAdmin subdirectory of the application directory. If you modify the WebAdmin interface for the main domain, the modified pages will be used when a Domain Administrator of the main domain uses the WebAdmin Interface. The Server Administrator will see the framed version of the WebAdmin Interface (with the Settings, Domains, Directory, and Monitors realms) and the default WebAdmin files will be used to compose the Server WebAdmin Interface pages.
To modify the Server Strings, the administrator should follow the Strings link on the General Settings page. The Server Strings page appears (the actual page has much more strings):
To modify a Server String, enter the new text in the text field, and select the upper radio button. To change the string to its default value (displayed under the text field), simply select the lower radio button.
Click the Update button to update the Server Strings.