Home
Configuring
Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
Configuring users and servers
Topics in this section describe how to set up users and servers.
Configuring messaging
This section provides an overview of messaging and describes how to set up mail routing, how to set up and customize mail servers, and how to track mail.
The Domino® mail router
The Domino® mail router (the Router) is a special server task responsible for the delivery and transfer of the messages in MAIL.BOX. Delivery refers to moving messages from MAIL.BOX into a local mail file or database; while transfer refers to sending messages from MAIL.BOX across the network to another server.
Mailbox event notification
When the Domino® router is running in a steady state and a new message is deposited in MAIL.BOX, a copy of the message is made and placed on a mailbox event queue which is then used by a new MailEvent thread in the router. The router then uses this copy of the message without having to search MAIL.BOX to discover new messages nor perform a full note open for use in transfer or delivery. The message is cached and additional copies of this message are made as needed for multiple recipients. This router optimization prevents creating extra copies of the note.

Configuring
Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
- Configuring a network
  This section presents the planning concepts and setup procedures necessary for a successful HCL Domino® deployment over a network. It provides information on network protocols from a Domino perspective but does not attempt to provide general network information.
- Configuring users and servers
  Topics in this section describe how to set up users and servers.
  - Understanding the Server document
    The Server document is set up when you register a server. It contains many of the settings that define how your server operates.
  - Policies
    Use Domino® policy settings to control how users work with Notes®. A policy is a document that identifies a collection of individual policy settings. Policy settings documents define a set of defaults that apply to the users and groups to which the policy is assigned. You can change policy settings and they will be automatically applied to the assigned users and groups.
  - Defining default settings for Notes® user registration
    Before you register new Notes® users, you can specify default settings that apply to all users. Default settings simplify user registration and ensure user settings consistency. You can define many default settings, such as what mail server users have or what certifier ID to use for user registration. You can also specify a default workstation execution control list (ECL) to protect data from unauthorized workstation access.
  - Using groups
    Groups are lists of users, groups, and servers that have common traits. They are useful for mailing lists and access control lists. Using groups can simplify administration tasks.
  - Replicas
    You can make a database available to users in different locations, on different networks, or in different time zones, by creating replicas of the database.
  - Calendars and scheduling
    The calendar and scheduling features allow users to check the free time of other users, schedule meetings with them, and reserve resources, such as conference rooms and equipment.
  - Editing the notes.ini file
    The Domino and Notes notes.ini files contain the settings required for the server and client to operate correctly. If you modify or add settings in a notes.ini file, do so cautiously and never edit the file directly with a text editor.
  - Configuring directory services
    This section describes how to plan, set up, and use HCL Domino® directory services.
  - Configuring messaging
    This section provides an overview of messaging and describes how to set up mail routing, how to set up and customize mail servers, and how to track mail.
    - The Domino® mail router
      The Domino® mail router (the Router) is a special server task responsible for the delivery and transfer of the messages in MAIL.BOX. Delivery refers to moving messages from MAIL.BOX into a local mail file or database; while transfer refers to sending messages from MAIL.BOX across the network to another server.
      - Mailbox event notification
        When the Domino® router is running in a steady state and a new message is deposited in MAIL.BOX, a copy of the message is made and placed on a mailbox event queue which is then used by a new MailEvent thread in the router. The router then uses this copy of the message without having to search MAIL.BOX to discover new messages nor perform a full note open for use in transfer or delivery. The message is cached and additional copies of this message are made as needed for multiple recipients. This router optimization prevents creating extra copies of the note.
      - Starting, stopping, and restarting the mail router
        By default, when you start the server, the Router task automatically loads and starts. You can manually shut down and restart the Router to troubleshoot server and messaging problems. You can also disable automatic loading of the Router.
      - Recalculating the server's routing table
        The Router on each server maintains a dynamic routing table, which specifies the best route to each possible destination server. The routing table builds on information contained in the server's NOTES.INI file and in the Configuration Settings, Domain, Connection, and Server documents in the Domino® Directory.
      - Routing mail on demand to a specific server
        You can route mail to another Domino® server between scheduled intervals, forcing all mail in the transfer queue of the specified server to route immediately.
      - Using Domain documents
        Domain documents define the domains used in mail routing.
      - Routing internal mail
        Internal mail consists of messages sent between users within an organization and its local Internet domains. The Domino® mail router (the Router) uses both SMTP and Notes® routing to transfer messages between network servers, and handles messages in both MIME format and Notes rich text format. By default, the Router transfers local mail using the Notes routing protocol only. Within a given Notes named network, servers that use Notes routing automatically transfer mail among themselves.
      - Creating a Configuration Settings document
        Use the Configuration Settings document to set up LDAP, mail, mail routing, and MIME on an HCL Domino® server. You can also use this document to edit settings in the NOTES.INI file. A Configuration Settings document can define settings for all of your Domino servers in one HCL Notes® domain, for the servers in one specific group, or for one individual server.
      - Configuring Domino® to send and receive mail over SMTP
        Setting up an HCL Domino® server as an SMTP server consists of enabling two separate tasks: a listener task and a routing task. Enabling the SMTP Listener allows a server to receive mail over SMTP. Enabling SMTP routing lets the Domino Router send mail to other servers using SMTP.
    - The POP3 service
      POP3 (Post Office Protocol Version 3) is an Internet mail protocol that allows a user running a POP3 client -- for example, the Notes® POP3 client, Eudora Pro, or Microsoft™ Outlook Express® -- to retrieve mail from a server that runs the POP3 service. You can set up a Domino® server to run the POP3 service. The Domino server receives and stores mail for POP3 users, who can then connect to the server to retrieve their mail.
    - The IMAP service
      The Domino® server supports the Internet Mail Access Protocol (IMAP4rev1), defined in RFC 2060, for reading mail. The Domino IMAP service lets users with IMAP mail clients access mail files on a Domino server. The IMAP service differs from the POP3 service in that users are not required to download messages to a local computer to read and manipulate them. Users can work with messages over the network, while the messages remain on the server.
    - Customizing mail
      After you set up basic mail routing, you can customize the HCL Domino® messaging system to improve performance and meet the specific needs of your organization.
  - Configuring iNotes®
    HCL iNotes® provides HCL Notes® users with browser-based access to Notes mail and to Notes calendar and scheduling features. Administrators specify mail policy and security policy settings as well as notes.ini file settings to complete the full implementation of HCL iNotes.
  - Configuring Web servers
    This section describes how to set up the HCL Domino® Web server, and the Domino Web Navigator.
  - Setting up a cluster
    Setting up a cluster includes the tasks of creating and verifying that it is working correctly, and then setting up user access, mail, replications, size quotas, directory assistance, roaming, web navigation, and use of a private LAN in the cluster.
  - Configuring Widgets and Live Text
    Widgets and Live Text enables end users to see and act on Live Text in supported documents, including HCL Notes® mail, using XML extensions (widgets) created specifically for their use.
  - Domain Search
    Notes® client and Web users can use Domain Search to search an entire Domino® domain for database documents, files, and attachments that match a search query.

Mailbox event notification

When the Domino® router is running in a steady state and a new message is deposited in MAIL.BOX, a copy of the message is made and placed on a mailbox event queue which is then used by a new MailEvent thread in the router. The router then uses this copy of the message without having to search MAIL.BOX to discover new messages nor perform a full note open for use in transfer or delivery. The message is cached and additional copies of this message are made as needed for multiple recipients. This router optimization prevents creating extra copies of the note.

You can use NOTES.INI settings to limit the amount of memory used by open notes. The memory values are shared and maintained by mailbox event generation and any open router note.

For the following two NOTES.INI settings, RouterMaxEventMemorySizeBytes and RouterMaxEventMessageSizeBytes, if either of the maximum values specified are reached, the router falls back and searches mailboxes for new messages. New messages located during the search are not cached in the main message queue.

RouterMaxEventMemorySizeBytes

Memory limit for event generation.

The default setting is null, but when Domino® encounters a null value for this setting, it sets the value to equal the NSF buffer pool size divided by 5.
0 -- Disables the setting.

RouterMaxEventMessageSizeBytes

Maximum message size for any one message allowed to be copied and placed on the mailbox event queue.

The default value is null but when Domino® encounters a null value for this setting, it sets the value of 10000000 bytes (10 million bytes).
0 -- Disables the setting.

The following two NOTES.INI settings, RouterMaxQueueMemorySizeBytes and RouterMaxQueueMessageSize Bytes, provide limits for caching these notes in the main message queue for immediate use in delivery or transfer.

RouterMaxQueueMemorySizeBytes

Memory limit for main message queue caching of the note passed via mailbox event generation.

The default setting is null, but when Domino® encounters a null value for this setting, it sets the value to equal the NSF buffer pool size divided by 5.
0 -- Disables the setting.

RouterMaxQueueMessageSize Bytes

Message size limit for main message queue caching of notes.

The default value is null but when Domino® encounters a null value for this setting, it sets the value of 10000000 bytes (10 million bytes).
0 -- Disables the setting.