Hi thanks for that, but my second server is my linux based web site using cpanel...
Main Topics
Browse All TopicsHi all,
I have an Exchange server (SBS 2008) and I want to setup a backup email service so that email will continue to be received elsewhere in the event of my server being down.
- My website is hosted and I use cpanel to administer it.
- I have an mx record that points mydomain.com to mail.mydomain.com
Can I set up a lower priority mx record to point mydomain.com to itself? I assume so, but:
- what happens to the user accounts that I have on my server, do I have to replicate the accounts on my webmail or is a catch all ok?
- can I setup some kind of queue so that the email will be forwarded to my exchange server when it becomes available. If yes, how? cron?
Thanks,
Warren
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Warren,
The cPanel will allow you to create DNS 'MX' records so you can publish where your mail servers can be found. That's easy enough.
The second task is the ensure that you have a secondary mail server that is able to accept mail for your domain and then store it until your primary email server is available.
Consider if you want a backup server in case of a connectivity issue / telecommunications problem or some building specific issue at your main office. If so, then you need your backup server to be located elsewhere. In this example there are plenty of email backup facilities out there that will accept (catch all) ALL mail and store it until your server is live again. Generally these systems will check whether your email server is accessible at specific time intervals.
The other option is for you to setup your own backup email server as efq-uas has suggested, and ensure that the server can accept inbound mail from anonymous users. This could be configured to store mail in queue and then deliver to your main email server post-disaster.
The other option which will protect against hardware failure on a single server is clustering. This will be more expensive to implement and may not assit if you have an internet connectivity issue?
It all depends what you are trying to protect against.
Shaun
Hi
Pofix is very good for you. It will behave as a backup email server. and when first server will be up it will forward all emails to it.
http://www.cyberciti.bi
This article will help you a lot to configure it.
Thanks.
Personally I am not a fan of backup MX solutions as I find they are spam magnet.
I wrote this blog posting a while time ago one why they were a bad idea and an alternative.
http://blog.sembee.co.uk/a
Simon.
Hi Simon
When you say they are a spam magnet, would the domain get spammed more just for having a secondary MX record?
I have read your articles (great articles btw!) and you say the spammers would use the backup MX record to route their spam, however what if the main server has no spam protection in the first place, in this case the backup MX record shouldnt make spam worse right?, I'm thinking it would all end up going to the same server regardless of which MX record was used.
The most effective way of dealing with spam is to drop it at the point of delivery. If the email has already been accepted and then you attempt to reject it, you are at best wasting bandwidth, at worst causing back scatter, depending on how your backup MX record server deals with the messages.
I am running a long term experiment with one of my clients, where we have two internet connections in use. The same antispam software is protecting both connections (Vamsoft ORF). There are two MX records. The second MX record gets approaching double the amount of spam sent to it that Vamsoft deals with.
You don't get more spam, it is just that more of the spam that is sent to your domain is sent via the second host. If the second server does not have the same level of protection - even something as basic as recipient validation, then your infrastructure has to deal with more spam.
Simon.
I think I see what your saying, in my case I dont think it will make a difference however since the main server has no spam protection in the first place so spam coming in via different route is no worse then spam coming in on the main server.
All of our customers are SBS customers with no spam protection on the server, generally spam has not been much of an issue
Maybe mail relay services instead of backup mx is the answer, e.g. http://www.dyndns.com/serv
I'm trying to think of the best disaster plan, maybe the best way is to just setup a temporary IIS server to hold the mail and then once exchange is running to drop the mail in the pickup folder.
Hi all,
Thanks for all the contributions - they are all appreciated. I found this
http://forums.cpanel.net/f
and I was going to try it, but then I came up with my own solution.
I now have a Google mail account with Google Apps the address me@mydomain.com; it's free for small groups and organisations. Google Apps also allows MX records to point to it therefore, when my server is down, my 'me@mydomain.com' mail will redirect to google. Now for the best bit - Windows SBS 2008 has a POP3 mail reciever that I've set up for each account that simply checks (at a specified interval) the google account and delivers to an Exchange account on the server. So if the server is down, Google will get the mail. When the server is back up, it will retrieve what it missed from Google. It's perfect for my one server, 5 user small business.
Business Accounts
Answer for Membership
by: efg-uaePosted on 2009-06-14 at 01:08:14ID: 24622289
Hi
You need to setup one More Server in the Same Active Directory. so that All users are available to both Exchange Servers.
You need 2 Mx Records. with different IPs. One MX record with higher priority to your current server. and other mx will point to your backup server.
When one mail server will be down. Email will be automatically routed to other mail server.
You can also achieve this goal by clustring.
http://www.msexc hange.org/ articles_t utorials/e xchange-se rver-2007/ high-avail ability-re covery/dep loying-exc hange-2007 -sp1-ccr-c luster-win dows-serve r-2008-fai lover-clus ter-part1. html
Regard s,