Lotus Domino Administrator 8.5 Help - Setting advanced transfer and delivery controls

MAIL

Setting advanced transfer and delivery controls
1. Make sure you already have a Configuration Settings document for the server(s) to be configured.

2. From the IBM® Lotus® Domino® Administrator, click the Configuration tab and expand the Messaging section.

3. Click Configurations.

4. Select the Configuration Settings document for the mail server or servers you want to administer, and click Edit Configuration.

5. Click the Router/SMTP - Advanced - Controls tab.

6. Complete these fields in the Advanced Transfer Controls section:

Field Enter

Ignore message priority Choose 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 interval The 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.

7. Complete these fields in the Additional Controls section, and then click Save & Close:

Field Enter

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 failover Choose 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 transfer or deliver a message, it leaves the message in MAIL.BOX rather than generate a delivery failure report. Select this option if you want to be able to examine messages with failures. You can then access these messages and either release them, forward them, or delete them
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.

The change takes effect after the next Router configuration update. To put the new setting into effect immediately, reload the routing configuration.

Connection topologies for mail routing

Recalculating the server's routing table

Managing undeliverable mail in MAIL.BOX

Customizing the text of mail failure messages

Routing mail by priority

Restricting mail routing based on message size

Setting the message time-out value

Setting transfer limits

Controlling message delivery

Customizing message transfer

Glossary

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Glossary

Field	Enter
Ignore message priority	Choose 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 interval	The 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.

Field	Enter
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 failover	Choose 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 transfer or deliver a message, it leaves the message in MAIL.BOX rather than generate a delivery failure report. Select this option if you want to be able to examine messages with failures. You can then access these messages and either release them, forward them, or delete them 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.