Backup MX Servers

  • strict warning: Non-static method view::load() should not be called statically in /home/deeproot.in/site/modules/views/views.module on line 843.
  • strict warning: Declaration of views_plugin_display::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/deeproot.in/site/modules/views/plugins/views_plugin_display.inc on line 0.
  • strict warning: Declaration of views_plugin_display_block::options_submit() should be compatible with views_plugin_display::options_submit(&$form, &$form_state) in /home/deeproot.in/site/modules/views/plugins/views_plugin_display_block.inc on line 0.
  • strict warning: Declaration of views_handler_field_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/deeproot.in/site/modules/views/handlers/views_handler_field.inc on line 0.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/deeproot.in/site/modules/views/handlers/views_handler_filter.inc on line 0.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/deeproot.in/site/modules/views/handlers/views_handler_filter.inc on line 0.
  • strict warning: Declaration of views_handler_filter_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/deeproot.in/site/modules/views/handlers/views_handler_filter.inc on line 0.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/deeproot.in/site/modules/views/handlers/views_handler_filter_boolean_operator.inc on line 0.
  • strict warning: Declaration of views_handler_filter_many_to_one::init() should be compatible with views_handler_filter::init(&$view, $options) in /home/deeproot.in/site/modules/views/handlers/views_handler_filter_many_to_one.inc on line 0.
  • strict warning: Declaration of views_handler_filter_term_node_tid::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/deeproot.in/site/modules/views/modules/taxonomy/views_handler_filter_term_node_tid.inc on line 0.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/deeproot.in/site/modules/views/plugins/views_plugin_row.inc on line 0.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/deeproot.in/site/modules/views/plugins/views_plugin_row.inc on line 0.

Overview

Our Backup MX Services are aimed at primarily helping organisations improve the availability of their email services.

The most conventional way of deploying email servers is to have one MX (DNS) Record and point that to their Mail Server. This sort of a conventional deployment (with just one MX Record), however, is fraught with a lot of problems.

  • If your primary mail server is down, other mail servers have no other way of sending emails to you.
  • If your mail server is down for quite a long time, then those mails might even bounce back to their senders because your mail server wasn't able to receive those emails.

Multiple MX Records

Having multiple MX records and having a backup MX server is one way of ensuring that you can always receive emails irrespective of whether your primary deepOfix mail server is up or not.

The way mail delivery over SMTP works, mail servers sending mails to you will try the second mail server listed in DNS if the first (highest priority) one is not accessible for whatever reasons.

Multiple MX Records of the same priority

Two MX Records of the same priority enable you to fairly distribute your incoming email load across two mail servers. In other words, in this case, it is possible that all other servers use both of them with the same level of importance and they would connect on an average to both of them.

This way you distribute the load and you don't have too many SMTP connections coming in to your mail server or coming in to a single mail server. Half of them at least go to the Backup MX which takes care of receiving those emails and pushing them back to your mail server over another secure connection.

Some background information on the role of DNS records in mail delivery

MX Records are a type of DNS Record which publish information about where others can send emails to you. This means that if one want to know the IP address or the location of your mail server, one would need to query the MX record for your email domain. Once that information is available, one can simply connect to the mail server and deliver my email to you.

The way the email mechanism has been designed, it has to take care of failures in some way. So if one tries to connect to your mail server and your mail server doesn't respond or is down (for a variety of reasons like there is no power, the internet link is down or there is a problem in your server hardware and the likes), then the mail server would keep trying to reach your mail server for a certain period of time.

Now each mail server like that on the internet has its own setting on how long it should keep trying to send emails to you. It might make the first attempt to send an email to you right now and if that fails your mail server might be configured to keep trying for another one day, or for very busy mail servers it might even be one hour (this could even vary to days and weeks depending upon the custom configuration settings). But whatever the time limit is, after it expires and if I'm still not able to reach your mail server, I'd have to send the mail back to the sender saying that your mail server is unreachable.

Deliverables

Setting up a Backup MX server

  • The first way is that you setup your own deepOfix server in your office or workplace and you contract out the Backup MX hosting to a service provider like us. We host the Backup MX on our servers. Thus, we receive the emails on your behalf (when the link to your primary mail server is down or busy) and consequently push it back to your primary mail server.
  • The second way is to have your own server sitting in another location where all it does is receiving emails for you as a backup and then push these emails backup to you. We again use deepOfix to do this setup for you.
  • A third option would be to put this second server in a data center where it could also host your websites and so on but as an additional feature it receives emails for you on a secondary MX and pushes them back to your primary mail server.

FAQ