Identification |
||
Host Server |
The full NDS context name of the messaging server. The host is selected when creating the Messaging Server object. IMPORTANT: You must restart the ims executable to effect any changes in this property. For more information on loading and unloading the messaging server, see the Novell® NetMail® Administration Guide at http://www.novell.com/documentation.
|
|
Postmaster |
The user assigned to manage the messaging server. This user can also receive copies of bounced messages. (See the CC PostMaster property in the NMAP Agent's Options page.)
Click the Browse button IMPORTANT: The Postmaster must belong to a Global Domain. You cannot designate a Hosting Domain user as the messaging server Postmaster. For more information on Global and Hosting Domains, see the Novell NetMail Administration Guide at http://www.novell.com/documentation. IMPORTANT: Do NOT delete the User object designated as the messaging server Postmaster. You must reassign the Postmaster before deleting the existing Postmaster User object. Deleting the Postmasters User object changes the Messaging Server object to type Unknown. Consequently, the Messaging Server object appears with a ? in NDS®. To reset the Messaging Server object type, you must run the IMSPMFIX utility. You can download this utility at http://www.novell.com/coolsolutions/netmail/ features/a_product_updates_nm.html. IMPORTANT: You must restart the ims executable to effect any changes in this property. For more information on loading and unloading the messaging server, see the Novell NetMail Administration Guide at http://www.novell.com/documentation.
|
|
Official Domain |
The Internet domain serviced by the current messaging server (such as abc.com or 123.net). All system messages, such as those sent to the Postmaster, use this domain. Additionally, if the messaging server is running the NMAP Agent, the Official Domain is the default domain for users within the NMAP Agents context. IMPORTANT: For the Official Domain, a Global Domain is required; a Hosting Domain is not allowed. For more information on Global and Hosting Domains, see the Novell NetMail Administration Guide at http://www.novell.com/documentation. You must register the Official Domain in DNS before the messaging system can send and receive mail via the Internet. NetMail can share an Internet domain with other messaging systems. NetMail can run alongside any application that supports Internet standards including groupware applications such as Novell GroupWise®, Lotus* Notes*, and Microsoft* Exchange. For information about domain sharing, see the Novell NetMail Administration Guide at http://www.novell.com/documentation. IMPORTANT: Changes to this property are effective within 5 minutes.
|
|
Temp Directory |
The drive or volume and, optionally, the directory where the NetMail Agents write temporary files. IMPORTANT: You must restart the ims executable to effect any changes in this property. For more information on loading and unloading the messaging server, see the Novell NetMail Administration Guide at http://www.novell.com/documentation.
|
|
DBF Directory |
The directory where the NetMail alias database, address book, and queue client files are stored. NOTE: On Linux*, SSL certificates are also stored in the DBF directory. The queue client files track every NetMail agent that has registered with NMAP so, if the NMAP server goes down, the NMAP Agent can re-establish its client connections. Queue client files are most pertinent in distributed environments where NMAP clients can reside on different messaging servers than the NMAP Agent. IMPORTANT: You must restart the ims executable to effect any changes in this property. For more information on loading and unloading the messaging server, see the Novell NetMail Administration Guide at http://www.novell.com/documentation.
|
|
Resolvers |
The IP address of one or more DNS servers that resolve host names into IP addresses. IMPORTANT: You must restart the ims executable to effect any changes in this property. For more information on loading and unloading the messaging server, see the Novell NetMail Administration Guide at http://www.novell.com/documentation.
|
|
Distributed Processing |
Determines if the messaging server interacts with other messaging servers in the Internet Services container using the NMAP protocol. By default, Distributed Processing is disabled. This creates a standalone messaging server; that is, the messaging server does not search the Directory tree for Internet Services and its associated messaging servers. If Distributed Processing is enabled, the messaging server searches the Directory tree for Internet Services and its associated messaging servers. You must disable distributed processing to create a standalone messaging server. NOTE: For help in determining whether distributed or standalone messaging servers best suit your messaging system environment, see the Novell NetMail Administration Guide at http://www.novell.com/documentation. IMPORTANT: You must restart the ims executable to effect any changes in this property. For more information on loading and unloading the messaging server, see the Novell NetMail Administration Guide at http://www.novell.com/documentation.
|
|
Connection Manager |
If enabled, enter the full NDS context name of the server running the Connection Manager. You must have a Connection Manager running in your messaging system to configure this option. IMPORTANT: For Connection Manager to have a comprehensive record of all authenticated users, you can only have one Connection Manager per messaging system. Connection Manager tracks the IP addresses of authenticated users. If this field is completed, any agent running on the current messaging server can query the Connection Manager Agent to verify that a user has authenticated with the system. For example, the SMTP Agent utilizes the Connection Manager Agent for SMTP-after-POP authentication. IMPORTANT: Changes to this property are effective within 5 minutes. NOTE: When you install NetMail 3.5 with Novell Nterprise Linux Services, Connection Manager is automatically configured and enabled.
|
A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For more information, see Legal Notices.