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.
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.
Customizing message transfer
You have many options when controlling the transfer of messages between servers in your HCL Domino® system.
Enabling automatic dead mail processing
Dead mail occurs when the router can't deliver or transfer either a message to the intended recipient or a non-delivery report to the sender. You can configure the router to automatically retry delivery of dead mail and if unsuccessful delete it from mail.box after a specified number of retry attempts.
Monitoring automatic dead mail processing
When automatic dead mail processing is enabled, the router logs information about whether dead mail is successfully transferred and when dead messages are deleted. You can also use statistics to monitor dead mail processing.

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.
    - 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.
      - Controlling messaging
        After you set up basic mail routing, use HCL Domino® administrative controls to customize the messaging system to your environment. Using the Domino Administrator and other tools you can change settings that affect routing performance, protect the system from unauthorized use, schedule message transfer, and ensure efficient use of network bandwidth and storage space.
      - Controlling message delivery
        Message delivery occurs when the Router deposits a message in the recipient's mail file. You can control how the Router behaves when delivering messages to mail files on the HCL Domino® server.
      - Specifying a reverse-path setting for forwarded messages
        You can specify how the router handles messages that are forwarded by a user mail rule send copy to action. By default, delivery status reports (DSNs) are requested not to be sent to the email account that forwards the message by setting a null reverse-path. This can cause some spam filters to reject the message.
      - Setting server mail rules
        You can create content filtering rules for that define actions to take on certain messages. When a new message that meets a specified condition is deposited in MAIL.BOX, Domino® automatically performs the designated action. Possible actions include journaling a message, moving it to a database, refusing to accept or deliver a message, changing the routing state of a message, or stopping the processing of subsequent rules. Rule conditions are based on content in the message headers or in the message body.
      - Enabling scheduled messages
        Domino® 10 and later mail servers support the scheduled delivery of mail messages. For example, a user can compose a message on a weekend and schedule it to be sent during the work week.
      - Setting up message recall
        Message recall provides Notes® client users with the ability to recall mail messages after they are sent. This feature is useful when a Notes client user has accidentally clicked Send and then needs to retract the message in order to complete or modify the message content.
      - Customizing message transfer
        You have many options when controlling the transfer of messages between servers in your HCL Domino® system.
        Restricting mail routing based on message size
        You can set size limits on messages to prevent large messages from consuming network bandwidth. There are two types of message size limits: a maximum message size and a low-priority size range. Messages that exceed the maximum message size are returned to the sender as undeliverable. Messages that are smaller than the maximum size, but that fall within the specified size range, are marked low-priority and routed during off-peak hours (12 AM to 6 AM by default).
        Routing mail by priority
        Notes® users can click the Delivery Options button to specify a priority level -- high, normal, or low -- for each message they create. The priority level determines how quickly the Domino® Router transfers a message over either Notes or SMTP routing. If a user does not specify a priority for a message, the server treats it as normal priority by default.
        Generating delay notifications for deferred low-priority mail
        When Domino® routes all low-priority mail within the specified low-priority time range, the affected messages can remain in MAIL.BOX for a significant amount of time. A delay might not be noticed by users whose messages were intentionally sent as low-priority, but occasionally message priority is reduced unexpectedly, as, for example, when messages greater than a specified size are sent at off-peak hours. Unexpected routing delays can cause concern and result in calls to the help desk.
        Restricting users from sending mail to groups in the Domino® Directory
        By default, all users can send mail to groups defined in the Domino® Directory. To reduce unnecessary mail traffic, you can edit the reader fields for a Group document to restrict access to the group, specifying the users who are allowed to send mail to the group. Only users to whom you grant reader access can send mail addressed to the group. Users who do not have reader access to the group will not be able see the group name listed in the Domino Directory.
        Defining when to send transfer and delivery Delay reports
        You can define the amount of time a pending message can reside in the router's message queue before a Delay report is sent to the author of the undelivered message. This applies to all pending messages on any server on which you have enabled transfer and delivery Delay reports.
        Setting transfer limits
        Transfer controls affect how Domino® transfers messages between servers. They control the number of threads used, the number of hops allowed before a message fails, the low-priority mail routing time range, and the time-out and purge intervals. Transfer controls apply to both SMTP and Notes® routing.
        Setting advanced transfer and delivery controls
        You can set Notes® email advanced transfer and delivery controls.
        Enabling automatic dead mail processing
        Dead mail occurs when the router can't deliver or transfer either a message to the intended recipient or a non-delivery report to the sender. You can configure the router to automatically retry delivery of dead mail and if unsuccessful delete it from mail.box after a specified number of retry attempts.
        Monitoring automatic dead mail processing
        When automatic dead mail processing is enabled, the router logs information about whether dead mail is successfully transferred and when dead messages are deleted. You can also use statistics to monitor dead mail processing.
      - Customizing Notes® routing
        To customize HCL Notes® routing in your organization, you can xchedule routing for optimal efficiency, change the routing cost of connections between HCL Domino® servers, and restrict mail routing based on Domino domains, organizations, and organizational units.
      - Customizing SMTP Routing
        If you enabled SMTP routing, you can customize it by stopping and starting the SMTP service, changing the inbound and outbound SMTP port settings, restricting inbound SMTP routing, restricting outbound SMTP routing, and specifying inbound and outbound MIME settings.
      - Setting up and using message disclaimers
        Message disclaimers are notices -- usually short text blocks -- that are added to email messages. They are often used by organizations in an attempt to protect the organization's legal interests. For example, message disclaimers can be used to limit an organization's exposure to vicarious liability, that is, to limit the organization's responsibility for the actions of its employees. This type of disclaimer informs the message recipient that the organization is not responsible for anything written by the author of the message.
      - Mail journaling
        By default, after the Notes® Router processes a message, it does not retain a copy of the message. That is, after ServerA successfully sends a message to ServerB, the Router on ServerA deletes the message from its MAIL.BOX database. Likewise, when ServerB successfully transfers or delivers the message to the next server on the routing path, the Router on ServerB removes the message from its MAIL.BOX database.
      - Setting inbound and outbound MIME and character set options
        You can control how servers convert MIME items and international character sets for inbound and outbound messages by specifying options on the Configuration Settings document.
      - HTML rendering for mail
        By default, HTML-formatted mail messages -- for example, mail newsletters -- are rendered using these browsers. The default use of these browsers ensures that HTML-formatted emails are readable and appear to the recipient as the sender intended. Note that such rendering is for reading only. If a user edits an HTML-formatted mail message or forwards or replies to one, the new mail message is rendered using the Notes® embedded browser, and may not retain all of the original HTML formatting.
  - 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.

Monitoring automatic dead mail processing

When automatic dead mail processing is enabled, the router logs information about whether dead mail is successfully transferred and when dead messages are deleted. You can also use statistics to monitor dead mail processing.

Procedure

Use the following statistics to monitor dead mail processing:


Command	Description
Show Stat Mail.Dead.RetryCount	Number of dead messages retried since server startup. For example, if message 1 was retried once and message 2 was retried three times, count is 4.
Show Stat Mail.Dead.DeletedCount	Number deleted dead messages since server startup. Dead messages are deleted when Dead mail delivery attempts allowed value has been reached or is set to 0. Deletion also occurs in some error cases, such as when server is unable to determine the address to retry.

The following example shows output for these two commands with Dead mail delivery attempts allowed set to 3. It shows that one message was retried 3 times and then deleted. Console output for Mail.Dead.RetryCount and Mail.Dead.DeletedCount.