Debian Email Backup Server

We have an Exchange 2010 server as our primary mail server.  We want to put in a backup email server in case our Exchange server goes down.  I've set up IMAP servers before with Debian, so I was thinking about setting one up.  The idea would be to hold all the emails destined for the Exchange 2010 server on the Debian server while the Exchange 2010 server is down.  However, when the Exchange 2010 server comes back up, the Debian server would send all those emails it had been queuing up to the Exchange server for delivery.

Not quite sure how to set the Debian server up like that.  Any suggestions?
sedberg1Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PapertripCommented:
What you are trying to accomplish is pretty straight forward and very common.

Here are some instructions on how to do it using Postfix

http://www.howtoforge.com/postfix_backup_mx
http://www.postfix.org/STANDARD_CONFIGURATION_README.html#backup

The inherent problem with backup MX's is that they are regularly targeted by spammers since they assume the backup will not have as stringent anti-spam policies in place as the primary.  Make sure you implement ample anti-spam/spoofing techniques on your backup MX.

Keep in mind also that senders will queue and periodically retry sending of mails when the receiving MX is unreachable.  If you don't need to access all queued mails immediately once the primary is back online, then a backup MX just might be unnecessary -- all depends on your needs and environment.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
arnoldCommented:
It is a fairly straight forward. 1, you need to have two public IPs.
Pointing each ip to each server.
Depending on the email server you pick the configuration is to accept emails for the domain, while not treating the domain as either local nor virtual. Within the transport section, the Debian mailserver will point to the exchange as the destination.  Some mail servers have tern capabilities such that when exchange comes backup it could issue an tern to the Debian server to transmit the emails now rather than waiting while the Debian server's queue is being processed.
0
sedberg1Author Commented:
Papertrip, that first link is AWESOME!!!!

Quick question, if MX1 becomes available again, according to the article, MX2 will keep attempting to push the queued up emails to MX1 but doesn't say how often.  Is there a way to manually push the emails from the queue on MX2 so I don't have to wait?
0
The Five Tenets of the Most Secure Backup

Data loss can hit a business in any number of ways. In reality, companies should expect to lose data at some point. The challenge is having a plan to recover from such an event.

PapertripCommented:
Absolutely, just issue postqueue -f on the backup.

There is also the SMTP ETRN command which arnold mentioned, either will work just fine.

http://www.postfix.org/postqueue.1.html
http://www.postfix.org/flush.8.html
http://www.postfix.org/ETRN_README.html
0
arnoldCommented:
Etrn, and the various options that were previously used by the primary to connect to the secondary and trigger the immediate transmission of the email queue are not available by Discussion
http://www.google.com/search?q=exchange+2010+etrn

Given that the email has already been delayed by the outage of the primary, what is the issue that once it has recovered why demand the immediate transmission which might pound the server and lead to once gain it becoming non responsive.
0
sedberg1Author Commented:
My mistake about not awarding points to the correct post.  I should have awarded the points to this post:

"What you are trying to accomplish is pretty straight forward and very common.
Here are some instructions on how to do it using Postfix

http://www.howtoforge.com/postfix_backup_mx
http://www.postfix.org/STANDARD_CONFIGURATION_README.html#backup

The inherent problem with backup MX's is that they are regularly targeted by spammers since they assume the backup will not have as stringent anti-spam policies in place as the primary."
0
arnoldCommented:
Post a question in community support to reopen this question so that you can make the corrections.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.