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 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.
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.

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.
- Editing the NOTES.INI file
  You should rarely, if ever, need to modify a server's or client's NOTES.INI file. The NOTES.INI file contains many settings that Domino® and Notes® rely on to work properly. An accidental or incorrect change may cause Domino or Notes to run unpredictably. Therefore, you should edit the NOTES.INI file only if special circumstances occur or if Support recommends that you do so.
- 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.
    - 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.

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.

About this task

You can use the Configuration Settings document or the NOTES.INI file setting, RouterUserRuleForwardReversePath, to specify the reverse-path setting. If both settings are used, the NOTES.INI file setting takes precedence over the setting in the Configuration Settings document.

Procedure

Make sure you already have a Configuration Settings document for the server(s) to be configured.
From the Domino® Administrator, click the Configuration tab and expand the Messaging section.
Click Configurations.
Select the Configuration Settings document for the mail server or servers you want to administer, and click Edit Configuration.
Click the Router/SMTP > Restrictions and Controls > Delivery Controls tab.
In the Reverse-path for forwarded mail field, choose one of these settings:
- Set reverse-path to null -- Default setting. Delivery status reports are not sent.
- Preserve existing value -- Leave the setting as is. The message originator, that is, the person who originally sent the message, may receive delivery failure reports.
  Note: There are other methods of requesting that delivery status notifications, or delivery reports, should not be sent for these forwarded messages. For example, if DSN is not enabled on an SMTP server, the default behavior for most SMTP servers is to send failure reports.
- Use recipients Internet address -- Delivery failure reports are sent to the current recipient's Internet address, that is, the email account that forwards the message.
  Note: The Use recipients Internet address setting can cause loops.
- Construct undeliverable return address -- Prepend "nobounce" to the recipient's Internet address resulting in a non-deliverable return address.
Click Save and Close.