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.
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.
Enabling a server to receive mail sent over SMTP routing
To set up a server to receive SMTP-routed messages, you must enable the SMTP Listener. Then the server can "listen" for SMTP traffic over the TCP/IP port (usually port 25) and receive SMTP messages in the MAIL.BOX database(s).

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.
        Preparing to send and receive mail to the Internet
        Use these steps to ensure that your system is ready to send mail to and receive mail from the Internet or another private SMTP network.
        Setting up SMTP routing to external Internet domains
        To send messages over SMTP to destinations outside of the local Internet domain -- for example, to the Internet or another private network -- you must enable external SMTP routing.
        Setting up SMTP routing within the local Internet domain
        You can set up servers to use SMTP routing when transferring messages to other servers in the local Internet domain. You can enable SMTP routing on every server or only on servers that route to destinations outside of the Notes® named network. For example, you may not have a direct IP connection between all the servers in one TCP/IP Notes named network and all the servers in another. You may still require that all messages moving from one Notes named network to another be routed through hub servers.
        Enabling a server to receive mail sent over SMTP routing
        To set up a server to receive SMTP-routed messages, you must enable the SMTP Listener. Then the server can "listen" for SMTP traffic over the TCP/IP port (usually port 25) and receive SMTP messages in the MAIL.BOX database(s).
        Setting up how addresses are resolved on inbound and outbound mail
        To ensure that messages are properly routed, you can configure the addressing and lookup options such as forwarding addresses, specifying a smart host, allowing Domino® to accept mail for multiple Internet domain, specify how Domino looks up recipients of incoming SMTP messages and other related actions.
        Setting up a forwarding address
        A forwarding address allows users who have Person documents in the Domino® Directory to have their mail forwarded to another address.
        Setting up a smart host
        A smart host is a directory server to which SMTP-routed messages are sent when the message recipient cannot be found in the Domino® Directory or other secondary directories configured on the server.
        Using a Global Domain document to set up a server to receive mail for multiple Internet domains
        Every organization has a primary Internet domain name -- for example, renovations.com -- by which it is known to the rest of the world. By default, Domino® considers the local, primary Internet domain to be the domain specified in the server's host name. For example, for a server with the host name Server1.renovations.com, both Server1.renovations.com and renovations.com are considered local Internet domains. The server does not accept messages addressed to recipients in any other Internet domain.
        Specifying how Domino® looks up the recipients of incoming SMTP messages
        When Domino® receives a message over SMTP, the message recipient is identified by an Internet-style address, in the format Genevieve_Martin@renovations.com, rather than a Notes-style address, such as Genevieve Martin/Renovations. To determine the correct destination mail file, Domino must match the SMTP address to a Person document in the Domino Directory. To find a match, the Router checks the $Users view of the directory. This view displays all name entries in all Person documents in the directory, including Internet mail addresses, as well as all user name variations, first names, last names, common names (CN), distinguished names (DN), short names, and soundex names.
        Specifying how Domino® looks up SMTP hosts when sending outbound mail
        You can specify how the Router determines the IP address(es) for destination SMTP systems (for example, the Internet). Known as address resolution, the method you select determines how the Router performs domain-name-to-IP-address translation.
        Enabling the Router to look up the sender's Internet address from the Person document
        When a Notes® client is configured to send mail for Internet recipients in Notes rich text format, a Domino® server must convert outbound mail from the client to MIME format for Internet mail transport over SMTP. The Domino server responsible for the conversion must ensure that all addresses in the message headers, including both the recipient and sender addresses, are in Internet mail (RFC 821/822) format.
        How Domino® formats the sender's Internet address in outbound messages
        Outbound SMTP messages always include the Internet address of the sender. Domino® can obtain the sender's address, sometimes called the reply address, from the sender's Location document, the sender's Person, or by constructing the address based on a default format or rules configured in the Global Domain document. To ensure that message replies are routed correctly to the original sender, reply addresses should match the sender's Internet address.
        Changing the default format for constructing the sender's Internet address on outbound mail
        When converting an HCL Notes® message for SMTP transfer, the Router replaces the Notes address of the sender with an Internet address. If the Router cannot determine the sender's Internet address, either from the InetFrom field of the Notes message, or the Internet address field of the user's Person document, it constructs an Internet address by combining the user's Notes name with HCL Domino® domain and Internet domain information.
        How Domino® uses Global domain documents during inbound and outbound SMTP routing
        When Domino® receives an inbound SMTP message, it attempts to determine whether the message is for a local recipient. When the Domino Directory does not include a Global Domain document, Domino accepts only messages addressed to users in the same Internet domain as the server, as indicated in the Fully-qualified Internet host name that appears in the Server document.
        Configuring Domino® to send mail to a relay host or firewall
        A relay host can be a server within your organization that routes messages addressed to destinations outside the local Internet domain. Often the same server acts as a firewall through which your organization funnels all messages outbound to the Internet. It can be an HCL Domino® server or another type of server -- for example, a UNIX™ sendmail server.
        Enabling SMTP outbound authentication to relay hosts
        You can use SMTP sender authentication to ensure that the sender of a message is a legitimate user of an SMTP server. SMTP sender authentication requires an account name and password for the destination SMTP server. The account name you use must be an account on the relay host SMTP server to which a specific Domino® server routes messages. The purpose of SMTP sender authentication is to authenticate the connection between a Domino router and an SMTP server.
        Routing mail over transient connections
        Sites that do not have permanent connections to the Internet, or to other servers on the Domino® network, can send and receive messages over a transient connection, such as a network dialup connection.
        Updating the SMTP configuration
        The SMTP service controls the SMTP listener on the Domino® server. By default, whenever you restart the SMTP service, and at two-minute intervals thereafter, the SMTP service automatically checks the NOTES.INI file, Configuration Settings document, and Server document to see if any settings have changed. If the service detects that settings have changed, it rebuilds its internal configuration to incorporate the changes.
        Validating Internet addresses
        Use the Validate Internet Address tool to validate the Internet address of users in an entire directory.
        Creating unique Internet addresses
        Use the Set Internet Address dialog box to create unique Internet addresses for users.
    - 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.

Enabling a server to receive mail sent over SMTP routing

To set up a server to receive SMTP-routed messages, you must enable the SMTP Listener. Then the server can "listen" for SMTP traffic over the TCP/IP port (usually port 25) and receive SMTP messages in the MAIL.BOX database(s).

About this task

Enabling the SMTP listener causes the server SMTP task to start up automatically every time the server starts. Disabling the SMTP listener prevents the SMTP task from starting up when the server starts.

Note: Do not add SMTP as a task to the task list in the NOTES.INI file or this feature will not work.

See the related links for more information about modifying the default SMTP port settings and configuring Domino® to send and receive mail over SMTP.

Procedure

From the Domino® Administrator, click the Configuration tab and then expand the Server section.
Select the Server document to be edited it and then click Edit Server.

On the Basics tab, complete these fields:

Table 1. Basics tab fields
Field	Enter
Fully qualified Internet host name	The server's complete combined host name and domain name, including the top-level domain. For example, smtp.renovations.com; smtp is the host name; acme is the second-level domain; and .com is the top-level domain. In the absence of a Global Domain document, the Router uses the entry in this field to determine the local Internet domain. Typically, the fully qualified host name is added to the Server document during server setup or by the Administration process (AdminP). A routing loop can result if this field does not contain a valid entry.
SMTP listener task	Choose one: Enabled to turn on the Listener so that the server can receive messages routed via SMTP routing Disabled (default) to prevent the server from receiving messages routed via SMTP routing

Click the Ports > Internet Ports > Mail tab.
In the Mail (SMTP Inbound) column, ensure that the TCP/IP port status is set to Enabled, and then click Save and Close.