↩ Troubleshooting

External MX entry

Some customers may choose to handle their email through an external service. If you choose to do so, we will need to configure our servers to ensure all of your internal mail is also delivered externally.

Any email sent from accountA.com on a given server to anything@accountB.com on the same server will be automatically routed internally, saving both time and bandwidth. Likewise, email sent from scripts running on the same server will also be routed internally. This is very standard behaviour for a mail server, however if you are handling your email externally it clearly presents a problem.

The solution is provided by the "localdomains" and "remotedomains" lists on all of our servers. These lists allow us to specify which domains should be routing email internally wherever possible, and which domains should never accept mail locally.

If you control your own DNS

If you have control over your own DNS and have decided to handle your mail externally, just ask us to remove your domain from "localdomains" to ensure any mail is sent out to your correct MX server.

If you use our DNS (Nameservers)

If you are using our nameservers but wish to have your email handled elsewhere, just let us know what MX entry your email provider requires for your domain name and we'll make the necessary changes for you. Alternately, you can handle this yourself via the "Edit MX entry" screen in your cPanel.

If you're a reseller

The most reliable method for a reseller to ensure a client domain handles email externally is to set the correct external MX Entry for their domain via the "Edit DNS Zone" screen and ensure the "Always accept mail locally" checkbox is NOT ticked. This will automatically remove the domain from the "localdomains" list. If you've configured it correctly, the following screen will then confirm that mail for the domain will not be handled locally.