Preparing to route mail to service users in a secondary domain

If service users are in a secondary Domino domain (a domain that is not the on-premises hub domain) prepare to route mail to the users through mail hub servers in the secondary domain.

About this task

Skip this procedure if all service users are in the on-premises hub domain.

To configure mail routing to service users in a secondary domain, create required Connection documents in the Domino directory of the domain, as described in this procedure. Also configure settings to optimize mail routing performance, as described in this procedure.

The steps in this procedure enable mail sent from on-premises users in the secondary domain to be routed to service users also in the domain. To route mail from on-premises users in other domains to the service users in the secondary domain, configure mail routing from the other domains to the secondary domain. You can route mail from other Domino domains or foreign domains that do not include Domino mail servers. For more information, see the topic Setting up Notes routing in the Domino® documentation.

To route mail from external users on the Internet to the service users in the secondary domain, configure an SMTP server to accept the mail. Then route the mail to a mail hub server in the secondary domain. For more information, see the topic Configuring Domino to send and receive mail over SMTP in the Domino documentation. You are responsible for configuring virus scanning and spam filtering on mail received from the Internet.

Procedure

Install and set up at least one Domino server in the domain to be a mail hub server, or use an existing server. Servers that route mail to the service must be Domino 8.5.1 Fix Pack 2 or a later version.

Create the following Connection documents in the Domino directory of the service user domain. These Connection documents enable servers to connect and route mail to the service.

Table 1. Connection document used to connect to the service
Field	Value	Additional information
Basics - Connection type	Local Area Network	None
Basics - Source server	*	None
Basics - Source domain	Name of the service user domain, for example, `PowerRenovations`	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 /SCN/Renovations, specify `*/SCN/Renovations`.
Basics - Destination domain	Name of the service user domain, for example, `PowerRenovations`	Specify the same value for the Source and Destination domains.
Basics - Optional network address	`notes.na.collabserv.com` or `notes.ap.collabserv.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

Table 2. Connection document used to route mail from mail servers in the on-premises 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 service user domain to route mail to the service, for example, `Mailhub2/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 name should not be CustomerMailHubs, which is a group that already exists for use in the service. 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 service user domain, for example, `PowerRenovations`	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 service user domain, for example, `PowerRenovations`.	Specify the same value for the Source and Destination domains
Basics - Optional network address	`notes.na.collabserv.com` or `notes.ap.collabserv.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 3. Connection document used to messages from mail hub servers in the service to service user mail servers
Field	Value	Additional information
Basics - Connection type	Local Area Network	None
Basics - Source server	`LLNMailHubs`	This is the group of mail hub servers in the service.
Basics - Source domain	Name of the service user domain, for example, `PowerRenovations`	Specify the same value for the Source and Destination domains.
Basics - Usage priority	Normal	None
Basics - Destination server	`LLNServers`	This is the group of mail and directory servers in the service.
Basics - Destination domain	Name of the service user domain, for example, `PowerRenovations`	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

Perform the followings steps to give each server access to the LLNServers group.
1. Open the Server document in the Domino Directory for the domain.
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.
Customize the routing retry interval by performing the following steps on each mail hub server:
1. From the Domino Administrator client, open a server in the domain.
2. Click Configuration > Server > Configurations.
3. Create or edit a Configuration Settings document that applies to the mail hub server.
4. Click Router/SMTP > Restrictions and Controls > Transfer Controls.
5. In the Initial transfer retry interval field, specify 1 minutes.
To allow the use of multiple transfer threads for mail routing, perform the following steps on each mail hub server:
1. Add the following setting to the server notes.ini file:
```
RouterAllowConcurrentXferToAll=1
```
2. Perform the following steps to limit the number of transfer threads used for routing to any single destination. This setting reduces the chance that routing to one destination over a slow connection will monopolize transfer threads and prevent routing to other destinations.
  1. From the Domino Administrator, click Configuration > Server > Configurations
  2. Add or edit a Configuration Settings document that applies to the mail server.
  3. Click Router/SMTP > Restrictions and Controls > Transfer Controls.
  4. In the Maximum concurrent transfer threads field, specify 4.
  Note: These steps allow the use of multiple transfer threads when routing mail to any destination, not only to the service. After users are provisioned for the service, monitor mail routing. Ensure that the setting does not negatively affect the performance of routing to destinations other than the service.