The virtual server can be configured to act as a secondary E-Mail server for domains hosted on other servers, such as another virtual server, or a Microsoft Exchange Server configured for Mail-On-Demand. When the primary E-Mail server is unavailable, messages will be sent to the secondary server, where they will be queued up for delivery once the primary server is available again. Configuring your Server for relayingIn order to prevent unauthorized use of your virtual server, only E-Mail for specified domains is allowed to be queued up and delivered. When a domain is added to a server, the domain is listed in the ~/etc/local-host-names file to tell sendmail that E-Mail to the domain should be accepted and delivered to local E-Mail accounts. In a similar way, you can set up your server to act as a secondary server by adding the domain to the ~/etc/relay-domains file.
DNS ConfigurationThere should already be an MX record in the DNS zone file for the domain which points to the primary mail server, if not one should be created. Usually, the default priority for MX records is 10. A new MX record with a lower priority (higher number) will need to be created that resolves to the virtual server. If we are providing DNS for the domain, a DNS request can be submitted to customer service asking to have an MX record added for the new mail server. Be sure to specify the new server's hostname or IP address and if it should be the primary or secondary mail server. Once your DNS changes have propagated (usually 24-48 hours after changed), E-Mail messages for the domain will be delivered to the primary server (i.e. the Exchange Server in the example above) when it is available, and if it is not accessible, messages will be queued up on the virtual server. When messages for a relay domain are queued up on the secondary server, it will check on a regular basis to see if the primary server is available. As soon as the primary server is accessible, the messages will be automatically dequeued to the primary server. |