Preparing for Notes mail routing 

---

You must prepare at least one IBM® Lotus® Domino® server to act as a primary mail routing hub between the service and your environment.

About this task

You can prepare two primary mail hub servers, to provide failover. Running the Domain Configuration tool later creates the Connection documents on the hub servers that automatically enable mail routing between them and the service.

You can route mail between the service and secondary mail hub servers in a different Domino domain than the primary mail hub servers. To do so, you must create the Connection documents manually.

The directory synchronization servers and primary mail hub servers are often in one Domino domain, but they can be in two domains. For example, you can use two domains, and have a directory synchronization server and a primary mail hub server in each domain. Or you can have directory synchronization servers in one domain and primary mail hub servers in another domain.

Procedure

1. Prepare at least one Domino server to be a primary mail hub server, or two, to provide failover. You can use servers that are already set up in your environment, or install and set up new servers.
   
• Make sure that the servers meet the server version requirements.
• Make sure that the servers meet the certifier requirements.
  
For more information, see the links at the end of the topic.

2. Give the LLNServers group access to each primary mail hub server:
1. Open the Server document of each primary mail hub server.
2. Click the Security tab.
3. Perform one of the following steps:
   
• Add LLNServers to the Access server field.
• Clear the users listed in all trusted directories check box and make sure that the Not access server does not prevent access to LLNServers.
  
  
3. If all on-premises users are in the same Domino domain as your primary mail hub servers, skip to the next step in this procedure. Otherwise, perform the following steps to enable service users and on-premises users in a different domain than your primary mail hub servers to send mail to each other.
   
1. To enable mail routing from service users to the on-premises users, create Connection documents that route mail from your primary mail hub servers to the on-premises user mail servers in the secondary domain. The service routes the mail to the primary mail hub servers, so these Connection documents are required to enable the routing to the final destination.
2. To enable mail routing from on-premises users in the secondary domain to service users, create Connection documents exactly as described in the following tables. These Connection documents enable servers in the secondary domain to route Notes mail directly to the service.
   
Table 1. Connection document that routes messages from mail hub servers in a secondary domain to mail hub servers in the service.

Field	Value	Additional information
Basics - Connection type	Local Area Network	None
Basics - Source server	Name of a local mail hub server or mail hub server group in a secondary domain to route mail to the service, for example, Mail1/Renovations or HubMailGroup. Other servers in the domain must be able to route mail to this server or group.	If you specify a group: The group name must occur before the name LLNMailHubs alphabetically. For example, use HubMailGroup but not MailGroupHub. The group type must be Servers only. The members must be the names of servers to route mail to the service.
Basics - Source domain	Name of the secondary domain, for example, WestRenovations	Specify the same value for the Source and Destination domains
Basics - Usage priority	Normal	None
Basics - Destination server	LLNMailHubs	None
Basics - Destination domain	Name of the secondary domain, for example, WestRenovations.	Specify the same value for the Source and Destination domains
Basics - Optional network address	notes.lotuslive.com or notes.ap.lotuslive.com, depending on the data center that your company uses.	DNS host name of the proxy server in the service.
Replication/Routing - Replication task	Disabled	None
Replication/Routing - Routing task	Mail routing	None
Schedule	Enabled	None



Table 2. Connection document that routes messages from mail hub servers in the service to user mail servers in the service

Field	Value	Additional information
Basics - Connection type	Local Area Network	None
Basics - Source server	LLNMailHubs	None
Basics - Source domain	Name of the secondary domain, for example, WestRenovations	Specify the same value for the Source and Destination domains.
Basics - Usage priority	Normal	None
Basics - Destination server	LLNServers	None
Basics - Destination domain	Name of the secondary domain, for example, WestRenovations	Specify the same value for the Source and Destination domains.
Basics - Optional network address	Leave blank	None
Replication/Routing - Replication task	Disabled	None
Replication/Routing - Routing task	Mail routing	None
Schedule	Enabled	None



Table 3. Connection document to provide the network address of any server in the mail hub servers group in the service

Field	Value	Additional information
Basics - Connection type	Local Area Network	None
Basics - Source server	*	None
Basics - Source domain	Name of the secondary domain, for example, WestRenovations	Specify the same value for the Source and Destination domains.
Basics - Use the ports	Appropriate TCP/IP port	None
Basics - Usage priority	Normal	None
Basics - Destination server	*mail_server_certifier	For example, if your service mail server certifier is /SMN/Renovations, specify */SMN/Renovations.
Basics - Destination domain	Name of the secondary domain, for example, WestRenovations	Specify the same value for the Source and Destination domains.
Basics - Optional network address	notes.lotuslive.com or notes.ap.lotuslive.com, depending on the data center that your company uses.	DNS host name of the proxy server in the service.
Replication/Routing - Replication task	Disabled	None
Replication/Routing - Routing task	None	None
Schedule	Disabled	None



4. Perform the following steps to configure the retry interval for routing mail from your environment to the service. Configure the retry interval for your primary mail hub servers and for any secondary mail hub servers that route mail directly to the service. This interval enables on-premises mail servers to find an alternate server in the service if the first server tried is unavailable.
1. From the Domino Administrator, click Configuration -> Server -> Configurations.
2. Create or edit a Configuration Settings document that applies to mail servers that route mail to the service.
3. Click Router/SMTP -> Restrictions and Controls -> Transfer Controls.
4. In the Initial transfer retry interval field, specify 1 minutes.
   

Parent topic: Preparing for a hybrid environment

Related concepts
Version requirements for on-premises Lotus Domino servers
Certifier requirements in a hybrid environment
Planning Lotus Notes mail routing in a hybrid environment

Related tasks
Planning Internet mail routing in a hybrid environment

Related information
Scheduling server-to-server replication
Example of integrating a secondary domain with the service