The trash, the service backup and platform failover do not address the same accident. A backup independent of the server can bring back a deleted message, even one deleted on purpose, provided it was backed up before deletion and the date is still within the retention period. When the server goes down, incoming mail waits at the sender’s end: what matters then is the time to restore service and how many messages you are willing to lose.
Updated October 20266 minOfficial sources cited
People say “it’s backed up” for very different mechanisms. Each one catches one type of accident, with one person who acts and one limit.
| Safety net | Who acts | What it catches | Its limit |
|---|---|---|---|
| Trash and recovery folder | The user, in their mailbox | A recent mistake | Short duration, and nothing if the mailbox itself is deleted or compromised |
| Service backup | The operator, on request | Returning a message, a folder or a mailbox to a past state | The retention period, and the interval between two backups |
| Platform failover | The operator, without a request | The outage: mail keeps arriving or resumes | Does not bring back a deleted message |
The copy that the vendor or host keeps for its own availability, on several disks or several servers, belongs to the third safety net. It protects against hardware failure. It does not protect against deletion: a deleted message is deleted immediately on every replica. This is the most common confusion between redundancy and backup.
Yes, within three limits.
Deliberate deletion deserves particular attention. A disgruntled employee who empties their mailbox, or an attacker who has taken over an administrator account, can delete messages and try to delete the backups too. Hence the value of a backup that no one can modify during its retention period, including an email administrator. The ANSSI guide on backup recommends isolating backup servers within the administration system, and advises examining how a WORM-type solution actually achieves immutability rather than taking the word on trust.
An independent backup lives outside the email system it protects. In practice:
The same guide recommends the “3-2-1” rule, which starts with three separate copies of the data, and defines an offline backup as a backup on a medium disconnected from any information system. These notions apply to email as much as to files; how they apply to documents is covered in versioning, replication and backup.
Example. In a 25-person firm (hypothetical case), an employee deletes a client’s folder by mistake, empties the trash, and only notices the following Monday. The recovery folder no longer holds anything useful. The previous Friday’s backup contains the folder. The operator restores it into the mailbox; only messages that arrived and were deleted between two backups are missing.
Email copes well with short outages. A sending server that cannot reach yours, or that receives a temporary error, keeps the message in its queue and retries. As long as the outage lasts less than the time after which the sender gives up, usually counted in days, nothing is lost: the mail arrives when the service returns. The guide migrating email without interruption explains this mechanism in detail. A filtering gateway placed in front of the email service plays the same role: it holds the accepted message until the server responds.
What users see is different: no more webmail, phones that stop syncing, messages that cannot be sent. That duration is what the first indicator measures.
RTO (recovery time objective, the maximum tolerable downtime): the target time to get the service running again. RPO (recovery point objective, the maximum tolerable data loss): the amount of data, expressed as a duration, that you accept to lose if storage has to be rebuilt from the last backup.
The RPO does not concern mail waiting at the senders’ end: that mail arrives when the service returns. It concerns messages already delivered to mailboxes, and user actions, since the last backup, in the event that the storage itself is lost. An RPO of under 2 hours means that at most two hours of that history would need to be rebuilt. These are objectives: ask how they are measured and tested.
A prolonged outage, the end of a contract or the acquisition of your provider may force you to change email services. Your domain and your addresses do not change: the MX record points to the new platform. The method, with coexistence, copy passes, and consistent SPF, DKIM and DMARC, is described in migrating email without interruption. It is not repeated here.
No. Redundancy also replicates deletions. It protects against hardware failure, not against an error or a deliberate deletion.
Generally not: the sender keeps it and retries. It is lost only if it is permanently rejected, or if the outage lasts longer than the sender’s give-up delay.
To go back after an error, often yes. To keep messages for several years, no: that is the role of archiving. See archiving messages.
Yes, because the retention clock is running. Upstream protection is the job of the filtering gateway; see protecting the email system you already have.
For Klytic Mail, all three safety nets exist and are separate.
Restoring a message, a folder or a mailbox is requested from support, specifying the item concerned and the approximate date. It is included in the event of a service malfunction, a deliberate deletion by an employee or an account deleted too early during a departure (up to 3 requests per month), or an attack suffered despite properly protected workstations. After an accidental deletion, a user error, or if workstations were insufficiently protected, it is handled as a paid support ticket. The dumpster folder, at no cost, remains the first resort. The procedure is described in restoring a message or a mailbox.
What the offer does not cover: self-service restore by users beyond the dumpster folder, and retention beyond 30 days through backup. To keep messages for several years, legal archiving is available as an option.
This page describes a general framework. The commitments that apply are those in your contract.
Consulted in October 2026.
During the trial, ask for a deleted message to be restored: you will see how long it takes, who acts and where it reappears.
Welcome offer
No-commitment trial. An advisor calls you back to understand your needs and prepare your Klytic workspace.