Corporate Email Services

Mail sent to you should not be lost even when your server is down

A power outage, internet failure, or planned maintenance can temporarily take your mail server offline and cause incoming messages to bounce. Secondary Mail Exchanger safely queues those messages on our infrastructure and delivers them in order when your server comes back online, preventing temporary outages from generating delivery failures for senders.

No mail loss FIFO queue, order is not broken Secondary MX record in DNS No additional software

Problem

A short outage, a permanent loss

When a mail server is unreachable for a few hours, the servers on the other side stop retrying at some point. The result is lost mail that you never knew about.

Mail arriving during the outage

A quote, order or official correspondence sent during maintenance, a power cut or a line failure bounces back. The sender says "I couldn't reach you" and you are not even aware.

Retry period is limited

The sending server retries for a limited period before giving up and returning a delivery error. You have no control over how long it keeps trying.

Planned maintenance is a risk too

Planned work such as server updates or migration is postponed for fear of stopping the mail flow. With a backup queue in place, that pressure goes away.

Solution

How does it work?

A secondary MX record is added to your domain name's DNS records. The rest happens by itself.

Normal flow

While your server is up, all mail is delivered directly to you; our server is invisible.

The moment of outage

When your server cannot be reached, sending servers try the secondary MX record, that is, us. The mail is accepted.

Secure queue

Mail is held in the queue in the order it arrived (FIFO). No error returns to the sender and no mail is lost.

Automatic delivery

When your server is reachable, the queue is emptied automatically; mail is forwarded to you in its original order.

Technical summary

Activation: a secondary MX record is added to your domain name
Queue logic: FIFO (first in, first delivered)
Compatibility with existing infrastructure: Postfix, Exchange, Zimbra, Carbonio and others
No additional software is installed on your server
No setting changes on the user side
You only need to tell us about planned maintenance in advance

How We Work

Not a call center, the team that does the work

We are not a provider that sells mass packages. We work with a small number of organizations, getting to know their setup. The feedback we hear most is this: "When we call, we reach the technical team without waiting."

You reach the technical team directly

There is no ticket queue, no operator reading from a script, no "I passed it on to the relevant department" answer. You reach the colleague who knows the subject and talk through the solution with them.

A team that knows your organization

You don't have to explain your system from scratch every time. Whoever set up your server is the one who looks at it when a problem occurs, and they approach it knowing its history.

Not a ready-made package, a setup built around you

If your need doesn't fit a standard package, we change the setup, not the package. As a team that has been in the field for years, we design the solution around your process.

Help

Frequently asked questions

How long is mail held in the queue?

The queue holds mail until your server becomes reachable. If the outage is prolonged, the queue time and alert thresholds that apply are set according to your organization; if you foresee a long outage, you only need to tell us in advance.

Can you read the mail in the queue?

No. The system only carries and delivers mail; the content is not read. If needed, we work under a confidentiality agreement.

Can we see the mail during an outage?

We can share with you the number and status of mail waiting in the queue. If you are expecting urgent correspondence, tell us; we follow its delivery as a priority.

Does it also do spam filtering?

The job of Secondary MX is continuity. For spam and virus filtering, see our PMG Hosting service, which is a separate layer; when the two are used together, all incoming traffic is both protected and secured.

Is there a solution for our outgoing mail too?

Yes. On the outgoing side, our Smart Host service is used to prevent delivery problems caused by blacklists and reputation.

Does activation cause an interruption on our server?

No. Only a secondary MX record is added to DNS; the existing flow does not change and users see no difference. Once the record has propagated, the protection is active.

Let's look at your MX records together

How do your domain's mail records look right now, and what happens in an outage? Let's see with a short check and, if needed, turn on the backup queue.

Write to Us