Configuration Settings document - Router/SMTP - Advanced - Controls tab
Miscellaneous Controls
FieldEnter
Logging levelChoose one:
  • Minimal - Domino logs all mandatory status messages and fatal error messages.
  • Normal (default) - Domino logs all minimal events, plus warning messages indicating conditions that do not cause processing to stop.
  • Informational - Domino logs all minimal and normal events, plus informational messages involving intermediate storage, MAIL.BOX access, message handling, message conversion, and transport status.
  • Verbose - Domino logs all minimal, normal, and informational events, plus additional messages that may help you troubleshoot system problems.
Note To prevent the log file from becoming excessively large, use Verbose logging only when troubleshooting specific problems.

Advanced Transfer Controls
FieldEnter
Ignore message priorityChoose one:
  • Enabled - The Router sends all messages as Normal priority.
  • Disabled - (default) The Router honors message priority settings assigned by the sender or another server process.
Note Do not enable this setting if you restricted Domino to routing messages of a specified size as low-priority, and want to confine routing of large messages to the specified low-priority routing time.
Dynamic cost reset intervalThe time, in minutes, after which the Router resets the costs for the various connections. For example, if the cost reset interval is 15 minutes and a network failure caused the Router to increase a connection cost from 1 to 2, the Router resets the connection cost to 1 after the 15 minute cost reset interval.

Additional Controls (Delivery and Transfer)
FieldEnter
Restrict name lookups to primary directory only Choose one:
  • Enabled - The router can only look up names and groups in the Domino Directory for the server's Domino domain. The router cannot look up names and groups in other directories that are available through Directory Assistance or Directory Catalog.
  • Disabled - (default) The router can look up names and groups in any directories available from the server.
Cluster failoverChoose one:
  • Disabled - If a recipient's server is unavailable, the Router does not automatically route mail through a clustered server.
  • Enabled for last hop only - (default) When the Router detects that a recipient's mail server (the last hop in the routing path ) is unavailable, it attempts to locate a clustered server and transfer the message to that server. For example, Server1 routes a message addressed to Jane Doe, whose mail file is on Server3. Server1 fails to connect to Server3, which is unavailable. Server1 checks the Domino Directory to see if there are any servers clustered with Server3. Server2 is clustered with Server3, so the Router on Server1 attempts to connect to Server2. If the connection is successful, the Router transfers the message to Server2.
  • Enabled for all transfers in this domain - When the Router detects that a server for any hop in the routing path is unavailable, it attempts to locate a server clustered with that hop server. If the Router can find another clustered server, it transfers the message to that server. For example, if the Router on Server 1 attempts to transfer to HubA but HubA is unavailable, the Router checks the Domino Directory to see if there are any servers clustered with HubA. Because HubB is clustered with HubA, the Router attempts to connect to HubB. If the connection is successful, the Router transfers the message from Server1 to HubB, which continues routing the message.
Hold undeliverable mail
  • Enabled - When the Router cannot deliver a message, it leaves the message in MAIL.BOX rather than generate a delivery failure report.
  • Disabled - (default) When the Router cannot deliver a message, it generates a delivery failure report.
Note If you configure MAIL.BOX to hold undeliverable messages, examine the database frequently to check for accumulated messages.

Failure Messages
Failure message for the conditions below are specified byChoose one:
  • Text file - The Router adds customized text to failure messages from external files. For each condition listed, enter the complete path to a text file that contains customized text you want to add to the default failure message.
  • Text - The Router adds customized text to failure messages from text entered in the Configuration Settings document. For each condition listed, enter the customized text you want to add to the default failure message.
Transfer failure Transfer failures occur when there is a transient connection failure between the servers -- for example, a network problem.

If the first field in this section is set to Text, enter text to add to the default transfer failure message; otherwise specify the path to a file containing the text -- for example, C:\DOMINO\DATA\TRANSFER.TXT.

Delivery failure Delivery failures occur when the server is unable to deliver the message to the recipient's mail file -- for example, if the recipient's mail file has moved and the Domino Directory has not been properly updated.

If the first field in this section is set to Text, enter text to add to the default delivery failure message; otherwise specify the path to a file containing the text -- for example, C:\DOMINO\DATA\DELIVER.TXT.

Message expiration Message expiration failures occur when Domino cannot transfer the message to its destination in a given period of time.

If the first field in this section is set to Text, enter text to add to the default message expiration notification; otherwise specify the path to a file containing the text -- for example, C:\DOMINO\DATA\EXPIRE.TXT.

Domain failure Domain failures occur when Domino cannot identify the destination domain for a recipient of a message. For example, if you send a message to jdoe@lotus.com and Domino cannot locate lotus.com in either the Domino Directory or the DNS, the server generates a domain failure message.

If the first field in this section is set to Text, enter text to add to the default message for domain failures, or specify the path to a file containing the text -- for example, C:\DOMINO\DATA\DOMAIN.TXT.

Server failure Server failures occur when Domino cannot connect to the destination server. For example, if you send a message to jdoe@lotus.com, and DNS instructs you to send mail for the lotus.com domain to mail1.lotus.com but Domino cannot connect to mail1.lotus.com, the sending Domino server generates a server failure message.

If the first field in this section is set to Text, enter text to add to the default message for server failures; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\SERVER.TXT.

Username failure User name failures occur when Domino cannot match the local part of an address to a recipient. For example, if you send a message to jdoe@lotus.com, but Domino cannot find jdoe in the Domino Directory, the server generates a user name failure message.

If the first field in this section is set to Text, enter text to add to the default message for user name failures; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\USER.TXT.

Size failure Size failures occur when Domino rejects a message because its size is greater than the maximum message size (which you can specify in the "Maximum message size" field on the Restrictions and Controls - Restrictions tab of the Server Configuration document) and generates a size failure message.

If the first field in this section is set to Text, enter text to add to the default message for size failures; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\SIZE.TXT.

Restriction failure Restriction failures occur when Domino rejects a message based on outbound Router restrictions. For example, if you send a message to jdoe@lotus.com, but lotus.com is listed in the "Deny messages from the following Internet addresses to be sent to the Internet" field on the Router/SMTP - Restrictions and Controls - SMTP Outbound Controls tab of the Server Configuration document, Domino rejects the message and generates a restriction failure message.

If the first field in this section is set to Text, enter text to add to the default message for restriction failures; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\RESTRICT.TXT.

Delay notification Low-priority routing delays occur when MAIL.BOX receives a message that is marked low-priority and the Router waits to process the message until the specified low-priority routing time (12:00 AM to 6:00 AM by default). If low-priority delay notifications are enabled for the message, the Router sends a delay notification to the originator's address.

If the first field in this section is set to Text, enter text to add to the default low-priority delay notification; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\DELAY.TXT

Note Domino R5.0.x specified this file using the MailTextFileForTransferDelays setting in the server's NOTES.INI file. If this setting is present, it takes precedence over the setting specified here.

Quota warning notification The Router sends Quota warning notifications to users whose mail files exceed their configured quota warning threshold.

If the first field in this section is set to Text, enter text to add to the default quota warning notification; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\WARNING.TXT.

Quota error notification The Router sends Quota error notifications to users whose mail files exceed their configured quota.

If the first field in this section is set to Text, enter text to add to the default quota error notification; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\QUOTA.TXT.