Your Email Provider Is Not a Backup

Most people treat their inbox like a filing cabinet. Fifteen years of receipts, contracts, photos your family sent, the offer letter for the job you have now — all of it just sits there in Gmail or Outlook or Yahoo, because it's always been there and nothing has ever gone wrong. That track record feels like proof the system is safe. It isn't. It just means the risk hasn't landed on you yet.

An inbox is infrastructure for receiving mail. It was never designed as an archive, and the fact that it quietly works as one for years doesn't change what happens the day it stops.

The Ways This Actually Goes Wrong

None of this requires a rare, dramatic event. These are ordinary failure modes that any large provider's own support forums will confirm happen routinely — we're describing the categories honestly, not any specific person's story.

Account lockouts. You lose access to your phone number or authenticator app, and two-factor authentication — the thing protecting your account — becomes the thing locking you out of it. Recovery flows exist, but they're built around proving identity to a machine, and they don't always resolve quickly or in your favor. Until they do, every email you've ever received is unreachable.

Accidental deletion. A wrong click, an over-aggressive "clean up my inbox" pass, an automated filter that routes something to Trash instead of a label. Most providers keep deleted mail for a limited window — typically around 30 days — before it's purged for good. Miss that window and it's gone, no matter how long you've had the account.

Provider policy changes. Storage tiers shrink, features move behind new requirements, dormant accounts get reclaimed. Google, for instance, can delete an entire consumer account — Gmail, Drive, Photos, all of it — after two years of inactivity, a policy it announced in 2023 (Google's storage-management page). We covered the more recent storage squeeze in detail in an earlier post. None of this is unique to Google — every provider reserves the right to change the terms your archive lives under, and you find out after the fact, not before.

The 2FA lockout death spiral. This one deserves its own line because it compounds. Recovery email points to another account you also can't access. Recovery phone number is out of service. The identity documents you'd need to prove it's really you take weeks to process, if the process even has a human on the other end. Each broken link in the recovery chain makes the next one harder to fix, and the whole time, your email — and everything routed through it, password resets, two-factor codes for other services — is out of reach.

Business and institutional risk. You leave a job and IT revokes your account same-day. A company shuts down and its domain lapses, taking every mailbox on it with it. A shared family or team account changes hands. In every case, the emails were never really "yours" to keep — they lived on infrastructure someone else controlled, and access ended when the relationship did.

What an Actual Backup Means

The classic rule for backing up anything important is 3-2-1: three copies of your data, on two different types of storage, with one copy offsite. Full 3-2-1 is overkill for most people's email, but the principle underneath it is exactly right: a copy that lives under the same conditions as the original isn't a backup, it's a duplicate.

For email, a lightweight version of that rule is enough:

Copy one: the server. Your live inbox, wherever it is. This is what you use day to day, and it's already covered — you don't need to do anything for this copy to exist.

Copy two: local, on a device you control. A full download of every folder — Inbox, Sent, Drafts, Archive, custom labels — saved to your own disk, independent of the provider's login, password, 2FA, or terms of service. This is the copy that survives a lockout, a deletion, or a policy change, because none of those events touch a folder sitting on your computer.

If you want to go further, a third copy on an external drive or a cloud storage account separate from the one you're protecting rounds it out. But copy two is the one that actually changes your risk profile. Most people have zero backup copies of their email. Getting to one is the whole game.

Doing It Manually, With Any Client

You don't need special software to get a local copy. Any IMAP-capable mail client can do it:

Add your account to Thunderbird, Apple Mail, or Outlook using IMAP (not POP, which can leave mail server-side inconsistently). Once it's connected and every folder has synced, most clients cache the full message store on disk — Thunderbird's is a plain folder of files under its profile directory, for example. From there you can copy that folder to an external drive or archive it manually, message by message, into .eml files via drag-and-drop or an export menu.

It works. It's also slow, easy to do partially without realizing it (skipping Sent or Drafts is the classic mistake), and something you have to remember to repeat, because a backup you did once two years ago is not a backup of what's in your inbox today.

Where MailVault Fits

This is the exact gap MailVault is built to close. It's a free desktop app for macOS and Linux that connects to your existing IMAP or OAuth email account and archives every folder as individual .eml files on your own disk — the same open, universal format any client can read, with no proprietary database locking your archive to one app. Manual, unlimited backups are free, full stop; your local data is never gated behind a paywall.

If you want it to happen automatically instead of "whenever you remember," scheduled backups that run on their own are a $4/month or $25/year premium feature — the yearly plan has a 14-day trial so you can see whether it’s worth it before paying anything.

Related reading: how to back up email before closing an account, how to keep emails after deleting them from the server, and what to actually look for in an IMAP backup tool.