Sign In
MailGuard · Emergency mode

When the mail system stops,work doesnot.

Inbound messages are rarely lost during an outage, the sending server retries. What is lost is working time. The emergency mailbox gives your people reading and replying back.

Request a demoExplore MailGuard

A mail outage costs working time, not data

The sender queue protects against loss. It does not protect against nobody being able to work.

Your staff stands still

Eighty people whose work runs on email lose eighty person-days on a single outage day. A backup does not change that, it restores afterwards.

The deadline belongs to foreign servers

How long a sender retries is decided by its configuration. Twenty-four to forty-eight hours is common. Nobody in your own house controls that.

Customers notice first

Delay notifications reach business partners before your own IT knows something is wrong. The first report of an outage usually comes from outside.

The backlog causes the second outage

After recovery the entire queued volume hits a system that is just starting up. That is a common reason why it breaks again right afterwards.

One switch, not a project

Your MX already points at Conbool, otherwise you would not have MailGuard. Nothing more is needed.

1. Detect

As the upstream instance Conbool sees immediately when your system stops accepting inbound mail. Detection requires repeated failures over a longer period so a brief hiccup does not trigger an emergency.

2. Provide access

Whatever could not be delivered is available to your people in the browser. Read, open attachments, reply, forward, compose.

3. Switch back

As soon as your system accepts again the notice disappears by itself. The emergency copy stays readable for the configured period and is then deleted automatically.

What the emergency mailbox does

Deliberately lean. It bridges an outage, it is not a second mailbox.

No migration, no MX change

No migration, no DNS change, no project. Emergency mode is a setting inside your existing MailGuard configuration.

Replies look normal

Sending runs through the familiar Conbool outbound path, with DKIM, disclaimer and outbound content inspection. Nothing changes for the recipient.

The thread stays together

Every message sent in emergency mode also goes as a blind copy to the sender themselves and lands in the mailbox once the primary system is back.

Manually triggerable

For maintenance windows and for cases where automatic detection reacts too late, emergency mode can be switched on by hand.

Configurable retention

The emergency copy is outage relief, not an archive. You set the period, after which deletion is automatic.

Permissions as usual

Each person sees only their own mail. Sign-in, two-factor and roles apply unchanged.

Emergency mailbox versus the usual answers

What continuity plans say, and what it actually delivers.

 
Conbool emergency mailbox
Backup and waiting
Messages are not lost
yes
yes, as long as the sender retries
Reading during the outage
yes
no
Replying during the outage
yes
no
Setup effort
one switch
none
Effective during the incident
yes
only after recovery
Satisfies NIS2 continuity of operations
yes
no, recovery only

This comparison describes operation across a company. For individual users, encryption inside the client remains a workable solution.

Frequently asked questions

Are emails lost during an outage?
Usually not immediately. The sending server queues the message and retries, typically for twenty-four to forty-eight hours. If the outage lasts longer, the sender receives a non-delivery report. The emergency copy remains readable at Conbool.
Do I have to migrate my mailbox to Conbool?
No. Your mailbox stays where it is. Emergency mode builds on the fact that your MX already points at Conbool.
What happens to messages answered during the outage?
They go out through the normal Conbool outbound path and additionally as a blind copy to the sender themselves. Once the primary system is back the reply sits in the mailbox and the thread stays complete.
Can anyone see someone else’s mail?
No. Each person sees only messages addressed to their own addresses. The same roles and the same sign-in apply as everywhere else in the Conbool account.
How long is the emergency copy kept?
You configure the period. The default is short because the copy is outage relief, not an archive. After expiry it is deleted automatically.
How is this different from a backup?
A backup restores after the incident is over. The emergency mailbox keeps operations running while it lasts. NIS2 requires both and calls them continuity and recovery.
What if we already have the archive?
Then you additionally hold a permanent, audit-proof copy of your business correspondence. The emergency mailbox solves a different problem, namely reachability during a running outage.
Can I trigger emergency mode myself?
Yes. There is a switch in the settings for planned maintenance windows and for cases where automatic detection reacts too late.

Verwandte Lösungen

Microsoft 365 Ausfall

Weiterarbeiten, wenn Exchange Online keine Nachrichten annimmt.

NIS-2 Betriebskontinuitaet

Aufrechterhaltung des Betriebs nach Artikel 21 fuer den Mailkanal.

NIS-2 E-Mail-Sicherheit

Alle E-Mail-Anforderungen nach Paragraf 30 BSIG im Ueberblick.

Microsoft 365 E-Mail-Sicherheit

Warum der eingebaute Schutz von Microsoft 365 nicht ausreicht.

See it on your own setup

We show emergency mode on your domain and your mailboxes without you changing anything.

Request a demoGet in touch