Exchange can be configured to act as a backup MX server for another domain. Your Exchange server would accept email for another domain whose server is down, and then it would send the email on when the server is back in operation.
This will avoid anyone getting delivery failure messages. However you cannot extract the emails from the queue using this method, as it is just a storage point.
However the best use of this method is purely as a backup service after the original has gone down. A dynamic DNS service would be used to point email traffic at the backup server. The setup of the dynamic DNS server has been covered on the authors blog here: The Problem with Backup MX Services and an Alternative (blog - opens in new window)
Internal Network Check
Make sure that you don't have this domain listed in your internal DNS information.
Exchange Configuration
Create a new SMTP Connector in Exchange.
- Open ESM, Connectors.
- Right click on Connectors and choose New, SMTP Connector.
- Give the connector a name that identifies it as the relay for this domain.
- On the General tab, change the option to "Forward all email through this connector to the following smart hosts" and enter the IP Address or DNS name of the other server in the box for Smart Host. If entering an IP address it needs to be enclosed in [ ]: [192.168.1.1]
- Under "Local Bridgeheads" add your Exchange server.
- On the "Address Space" tab, remove the default * and enter the domain name that you wish to store email for.
- Enable the option "Allow messages to be relayed to these domains"
- All other options can be left as default.
That should be it. Exchange will accept the email for that server, if it cannot connect to the smart host (the real email server) then the messages will queue. This will be a single queue in ESM.
Increasing Timeouts
If you are backing up a server that will be down for an extended period of time, then change the timeouts on the SMTP virtual server so that email stays in the queues longer. However do monitor the queues as that will affect all email that passes through the Exchange server.
Exchange 2003 Home Page - Site Home Page
Last Page Update: 05/03/2011
| More Content from Sembee Ltd. | ||
| Resources on exchange.sembee.info | Other Sites | Sembee Ltd. |
| Microsoft Exchange 2003 | Command Prompt Getting Started Guide | Microsoft Exchange Consultancy |
| Microsoft Exchange 2007 | Login Scripts | Director's Blog |
| Microsoft Exchange 2010 | MS Exchange Resources | |
| Microsoft Outlook | Knowledge Base search | |
| Exchange Networking Tasks | Recovery of MS Office content from Temp Files | |
| Amazon Store | Troubleshoot the Automatic Updates Client | |
| UK ISP Status Pages | ||
| © Sembee Ltd. 1998 - 2011. | ||
| Reproduction of any content on this web site is prohibited without express written consent. Use of this web site is subject to our terms and conditions. All trademarks and registered trademarks are property of their respective owners. This site is not endorsed or recommended by any company or organisation mentioned within and is to provide guidance only and as such we cannot be held responsible for any consequences of following the advice given.
Sembee Ltd. is registered in England and Wales at 33 Scrivens Mead, Thatcham, Berkshire, RG19 4FQ. | ||