Latest
What You Have to Decide Before Anybody WritesWriting It Before You Need ItCross Training Covered Everything Except the Role That Mattered MostBehind the Book: You Don’t Own Anything AnymoreBehind the Book: The Woke VirusBehind the Book: Galactic InvasionWhat’s New at The Writing King: Week of November 8, 2026Alexander Zhidkov: Decision MakingJessi Szurek: Expand Your RangeYou Don’t Own Anything AnymoreThe Budget Decided How My Department Was ShapedWhy Your Competitor’s Book Is Working and Yours Would NotWhy Are These Guys Smiling? A Business Book That Became a Wrestling MemoirPangram Wants to Decide Who Gets PublishedWhat You Have Enough Material For Right NowWhen a Book Is the Wrong ToolThe Woke VirusGalactic InvasionChatGPT Turns Four: From a Free Research Preview to GPT-6What’s New at The Writing King: Week of November 1, 2026Diwali: The Festival of Lights and the Story Behind the LampsHow Much Water and Power Does Heavy AI Use Take? I Ran My Own NumbersBad Boys: Ride or Die (2024)Vesuvius Day: The Teenager Who Wrote Down Pompeii’s Last DayAnti-Communism Week: Remembering the Writers Communism SilencedVoyager 1 One Light-Day: Fifty Years to Travel One Day of LightVellum Added an Optional AI Feature. A Pile-On Killed It in a Day.Are AI Subscriptions Losing Money? The Gym Membership Math Says NoAI Terms Every Writer Should Know, and Why Each One MattersWorking While Sick: What 24/7 On Call Cost MeHe Banned AI From His Writing Group. His Own Cover Got Called AI Slop.Who Writes the Fake Fan Mail Authors Get? Inside the Scam CompoundsSMS Appointment RemindersJoe Rockey: Ghostwriting His BookDarrell Stern: Stop Being Invisible, Become UnmissableFree BooksHow to Turn Your Expertise Into a Book People Want to Read | The Expert MethodWhat’s New at The Writing King: Week of October 25, 2026Challenger Remembrance Day: The Engineer Who Wouldn’t SignJoel Salomon: The Truth About MoneyReddit Is Putting Up a Login Wall. Wikipedia Won’t Be Far Behind.Victoria Chemko: The Body Is the First TechnologySir Patrick Stewart: A TributeA Year in the Bank: ADHD, Face Blindness and the Freedom to Walk Out | The Impossible Puzzles Show, Episode 326A Yale Economist Says We Won’t Be Missed. He Forgot the Bread Line.Walter Koenig: A TributeAI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.I Don’t Post Bad ARC Reviews. I Send the Author a Note.The Little Red Book of Stuff That Works!Your Kids Are Your Own Fault

Your Email Is Not an Archive

TL;DR: A woman I worked with stored her legal and accounting documents in the trash bin on her Mac because it saved her clicks, and one routine cleanup destroyed tens of thousands of files with no recovery. A Google user recently had an account disabled with no warning and lost an archive stored in Gmail the same way. Both people kept irreplaceable material in a place designed to be temporary, and in both cases the system worked exactly as built. If your only copy of something lives somewhere you don’t control, you’re one automated decision away from losing it.

I spent 33 years in enterprise IT watching people treat email like a filing cabinet. It isn’t one, and the day the account goes away, everything in it goes too.

The way providers set people up is the worst part of this subject. The storage is free, it grows every year, search finds anything, and nowhere on any screen does it say the whole pile can vanish on the say-so of a classifier. The people who get hurt aren’t reckless. They trusted every signal they were given, and the company that sent those signals carries none of the loss.

One of my help desk techs called me about a full disk. Ordinary call, ordinary fix. A user at a major national retailer had run out of space on her Mac and couldn’t save anything, so he did what any competent technician does in that situation. He emptied her trash and gave her back the room she needed. She had been storing her legal documents in the trash bin.

Not by accident. She’d worked out that she could right-click a file, send it to the trash, and it would sit there indefinitely without her having to open a folder, go to another folder, and drag anything anywhere. Fewer clicks. Same result, as far as she could tell. She had been doing it for a long time and it had worked every single time.

We’re talking about tens of thousands of documents. Legal files and accounting records. Nothing recoverable, because the trash is the one location on a Mac that backup software is told to leave alone. Why would you back up the place where deleted things go?

Nobody in that story did anything wrong in the moment. The tech applied the correct fix. She’d found a workaround that saved her time and never failed. The machine did exactly what it was designed to do. And a decade of records stopped existing on a Tuesday afternoon.

The same mistake with a different container

I saw a screenshot recently that made me think about her for the first time in years.

A Google account, disabled. No warning, no specific accusation, no human being to talk to. The notice said the account looked like it was being used in a way that violated policy, which is a classifier speaking. There’s a link to appeal, and the appeal goes to another automated system.

gmail-account-disabled

The person on the other end of that notice had been using Gmail as a document archive.

Different container, identical error. Both of them put material they couldn’t replace into a place that was never built to hold it, and both of them had years of successful use telling them it was fine. Neither had any reason to doubt it, right up until the day the system did exactly what it was built to do.

Why does storing documents in email fail?

An inbox is a delivery mechanism. People started treating it as storage because it never asked them to stop, and because search made retrieval good enough that filing seemed unnecessary. Twenty years of that habit builds an archive nobody ever decided to create.

Nothing about a mail service is built for retention. There’s no integrity check. There’s no version history for an attachment. There’s no export you’d want to bet on. Attachments get stripped, links to cloud files rot, and the whole structure hangs off one credential controlled by a company that has no contractual obligation to keep you. I wouldn’t hand anything I cared about to an arrangement like that.

Inbox archaeologyA hand-drawn geological cross-section titled Inbox archaeology, a cross-section of twenty years of filing. Above ground, a sign reads dig site access: one password, and a yellow bulldozer labeled automated classifier announces account disabled, appeal goes to another classifier. Below ground are the strata. The top layer, the Unreadocene, this year, is scattered envelopes, all unread. Next, the Forwardassic, about five years down, holds a fossil spine of Re: Re: Fwd: Re: Fwd:. The Attachmentaceous, about ten years down, holds a fossilized paperclip and a link to a cloud file, long rotted. The Pre-Searchian, about twenty years down, holds tax documents filed by never deleting them and a file called final_FINAL_v2. At the bottom is bedrock: your only copy of everything, with no integrity check, no version history, and export: good luck.Inbox archaeology(a cross-section of twenty years of "filing")DIG SITE ACCESS:one passwordAUTOMATED CLASSIFIER"Account disabled.Appeal goes toanother classifier."UNREADOCENE(this year)FORWARDASSIC(about 5 years down)ATTACHMENTACEOUS(about 10 years down)PRE-SEARCHIAN(about 20 years down)BEDROCKall unreadRe: Re: Fwd: Re: Fwd: Re: Fwd:(fossil spine, complete)attachmentlink to a cloud file(long rotted)tax documents, "filed"by never deleting themfinal_FINAL_v2.docYOUR ONLY COPY OF EVERYTHINGintegrity check: none. version history: none. export: good luck.
Inbox archaeologyA hand-drawn geological cross-section titled Inbox archaeology, a cross-section of twenty years of filing. Above ground, a sign reads dig site access: one password, and a yellow bulldozer labeled automated classifier announces account disabled, appeal goes to another classifier. Below ground are the strata. The top layer, the Unreadocene, this year, is scattered envelopes, all unread. Next, the Forwardassic, about five years down, holds a fossil spine of Re: Re: Fwd: Re: Fwd:. The Attachmentaceous, about ten years down, holds a fossilized paperclip and a link to a cloud file, long rotted. The Pre-Searchian, about twenty years down, holds tax documents filed by never deleting them and a file called final_FINAL_v2. At the bottom is bedrock: your only copy of everything, with no integrity check, no version history, and export: good luck.Inbox archaeology(twenty years of "filing")DIG SITE ACCESS:one passwordAUTOMATEDCLASSIFIER"Account disabled.Appeal goes toanother classifier."UNREADOCENE(this year)FORWARDASSIC(about 5 years down)ATTACHMENTACEOUS(about 10 years down)PRE-SEARCHIAN(about 20 years down)BEDROCKall unreadRe: Re: Fwd: Re: Fwd: Re: Fwd:(fossil spine, complete)attachmentlink to a cloudfile (long rotted)tax documents, "filed"by never deleting themfinal_FINAL_v2.docYOUR ONLY COPY OF EVERYTHINGintegrity check: none.version history: none.export: good luck.

The storage keeps getting bigger and it stays free. That teaches exactly the wrong lesson. Every signal the product sends says permanent. None of the terms say permanent.

What happens when a Google account is disabled?

Three things happen at once, and most people only see one coming. The mail becomes unreachable. That’s the loss people picture, and it’s the smallest of the three.

Email is not an archive

Then everything authenticated against that account dies with it. Cloud storage, photos, contacts, calendar. A person who kept a second copy of their documents in Drive discovers that the second copy was never a second copy, because it lived behind the same login.

Then the slow part. Every other service in their life has that address as the recovery contact. Password resets go to a mailbox that no longer accepts mail.

Verification codes go nowhere. Banking, hosting, domain registration and social accounts start failing one at a time over the following weeks, and most people never connect those failures back to the original event.

A deletion clock is running through all of it. Disabled accounts are eventually purged along with everything in them, and nobody tells you how long you have.

I think that’s the cruelest part of the whole setup. A company can hold years of somebody’s life behind an automated appeal and never owe them a date.

The tools only work in advance

I keep a local copy of my email in Thunderbird, and it’s worth being precise about what that does and doesn’t protect against, because it’s easy to set up in a way that fails silently.

An IMAP connection is a mirror. It syncs state, so delete something on the server and Thunderbird removes the local copy on the next pass. And IMAP logs in with the same account, so when the account goes dark, so does your way in. There’s no separate credential and no separate door.

Which means the sync is a window that’s open while the account is alive. What survives is whatever happened to be on your disk when it closed.

Getting a real local copy takes two steps.

Turn on message synchronization for every folder instead of accepting the default. That leaves plenty of folders as headers only. On a Gmail account the All Mail folder is the one that matters, because that’s where the archive is. Then let it finish. Mine took two days, and most people who start that download close the laptop halfway through and never realize they have a partial archive.

The same constraint applies to Google Takeout. Once you can’t sign in, you can’t request an export, and a disabled account gets only the limited download Google decides to allow. Every mechanism that would save you requires an account that still works. That’s why none of them are available at the moment you’d think to use them.

The backup that was not running

This next part caught me, and it’s why I’m writing this instead of nodding along at somebody else’s misfortune.

Every mechanism that would save you requires an account that still works.

My mail store sits inside my Documents folder. That’s covered by an offsite backup. That should be the end of the problem. It wasn’t. Backblaze doesn’t support Volume Shadow Copy, so when another application locks a file it can’t read it. It skips the file and tries again about an hour later. Their own documentation names mail clients and says the application has to be fully closed before its data file will back up.

I leave Thunderbird running permanently. So the single most important folder on my machine had been in a skip loop, and the backup client kept reporting success the entire time, because from its point of view nothing had failed.

That’s what a silent failure looks like. Not an error, not an alert, just a thing not happening while every indicator stays green. The fix is either closing the client daily, which depends on remembering, or a scheduled task that copies the profile folder somewhere the backup can read it. I prefer not to depend on my own habits.

Why is your email recovery address a security risk?

The archive question is about losing data. This one is about losing the ability to recover anything else, and it’s both worse and cheaper to fix.

If your password reset emails arrive in the account you’re trying to recover, you’ve built a loop, and it only reveals itself on the day the loop breaks. I’d put this near the top of the mistakes I see smart people make, because the fix is cheap and the failure drags every other account down with it.

I’m guilty of this and I’m correcting it. The move is a separate mailbox at a different provider, used for nothing except account recovery. Different company, different jurisdiction, different enforcement regime. A Google policy decision has no reach into it.

Keeping it empty is risk reduction. A quiet mailbox with no attachments and no forwarding rules gives the robots almost nothing to flag, and that’s what you want. You’ve removed the surface for the exact thing that happened in that screenshot.

The same reasoning applies to your second factor. If verification codes land in the dead account, or the authenticator backup lives in the same cloud storage, you’ve built the loop twice. Recovery codes printed and filed somewhere physical is the version that survives.

Email safeguards and where each one fails
Safeguard What it does Where it fails
Second copy in Google Drive Keeps documents in another place Lives behind the same login, so it dies with the account
Thunderbird over IMAP Keeps a local copy of mail Mirrors deletions and logs in with the same account
Google Takeout Exports the account Cannot be requested once you cannot sign in
Offsite backup of the mail store Copies the Documents folder offsite Skips files locked by a running mail client while reporting success
Separate recovery mailbox at another provider Receives password resets Holds up when kept empty, with no attachments or forwarding rules
Printed recovery codes Restore your second factor Survive, because they sit somewhere physical

How long does an email account security audit take?

Longer than an afternoon. If you have eighty accounts, which is common, moving all of them to a separate recovery address will take weeks. Each one is a login, a settings page buried in a different place, a verification step, and occasionally a support ticket because the provider won’t let you change it cleanly.

The saving grace is that you’re doing it before anything is wrong. Nothing forces you to finish. Nothing breaks while it’s half done. You can stop for a fortnight and pick it up again.

What makes eighty accounts tractable isn’t doing them in whatever order your password manager lists them.

Work in three tiers. First the accounts that own everything else: domain registrar, hosting, the mail providers themselves, anything holding business payment details. That’s maybe eight accounts and it carries most of the risk. Then the accounts with money or identity attached, meaning banking, brokerage, tax and insurance. Then everything else. That’s the bulk of the eighty and matters least. A forum login with a dead recovery address is an inconvenience.

An evening on the first tier gets you most of the protection available. The remaining seventy can take a year.

What should you do about your email archive this week?

I’m not going to hand you a backup regime. A regime is something people intend to do, and I’ve watched far too many of them die in a drawer. A five-minute task is something people finish.

Name the three things in your email you couldn’t reconstruct from anywhere else. Everybody has an answer within about a minute, and it’s usually a tax document, a signed contract, or photographs somebody sent years ago that exist nowhere else. Those three things are the entire problem, and downloading them takes five minutes instead of becoming a project.

Then check your recovery address on the four or five accounts that would hurt most to lose. If any of them point at the mailbox you’re worried about, that’s the loop, and moving one of them takes about two minutes.

Everything after that’s optional and can wait for the audit.

My take

Inboxes are temporary containers, and treating one as an archive bets your records on somebody else’s automated decision. Get a copy of everything irreplaceable onto storage you control this week. Move your recovery addresses off the account they’re supposed to rescue, and print your recovery codes. Work the accounts in tiers, domain registrar first. It’ll take weeks. Nothing breaks while you’re halfway through, so start.

The system worked as designed

What stays with me about the woman with the trash bin is that she wasn’t careless.

She was efficient. She found a shortcut, tested it against reality every day for years, and reality agreed with her every time. The failure was a gap between what the container was built for and what she was using it for, and nothing in the design of the machine ever revealed that gap.

The guy whose Google account got disabled is stuck in the same hole, with nobody at Google to call.

They almost certainly never considered that this could happen, because the category didn’t exist for them. We all plan for the failures we can picture. A dead drive, a stolen laptop, a fire. Those have been in the culture for fifty years. Nobody has a story about the account still existing and simply refusing to know them.

In both cases the machinery worked perfectly. The trash emptied. The policy enforced. Nothing malfunctioned, and that’s exactly the problem. A system that fails loudly gets fixed. A system that works exactly as designed doesn’t look like a risk until it takes something from you.

If you want the longer version of this thinking applied to a whole household, I wrote Family Cybersecurity about exactly this, and the same reasoning shows up in my work on twenty years of disaster recovery and on the years when ransomware turned laptops into bricks. The rest of the material sits in the Cybersecurity Hub. And if you have a body of hard-won operational knowledge like this and no book to put it in, that’s what my ghostwriting service is for.

Go and look at your trash bin. Then look at what you’d lose if your inbox stopped answering tomorrow.

Get anything that matters out of your inbox and into a place you control, with a backup somewhere else. Companies that sell free storage as a home for your whole life and then lock the door on a classifier’s hunch with nobody behind it to answer are selling a bad deal. They won’t warn you first, so the job falls to you, and it’s worth doing this week.

From the author
Family Cybersecurity by Richard Lowe

Family Cybersecurity
Thirty years of family photographs vanished in the middle of one night and none came back. Family Cybersecurity is about protecting the people in your house before that call comes.

Frequently Asked Questions

Is it safe to store important documents in your email?
No. An inbox is a delivery mechanism that people began treating as storage because it never asked them to stop. There’s no integrity check, no version history for attachments, no export worth relying on, and the whole archive hangs off one credential controlled by a company with no obligation to keep you as a customer.
What happens when Google disables your account?
The mail becomes unreachable, everything authenticated against that account dies with it including cloud storage and photos, and every other service using that address for password resets begins failing over the following weeks. A deletion clock also starts, and disabled accounts are eventually purged along with their contents.
Does keeping a local copy in Thunderbird protect your email?
Only if the sync finished before you needed it. An IMAP connection authenticates against the same account, so it dies when the account does. What survives is whatever was already on your disk. That means message synchronization has to be enabled for every folder and the initial download has to be allowed to complete.
Why does Backblaze skip Thunderbird mail files?
Backblaze doesn’t support Volume Shadow Copy, so it can’t read files that are locked by another application. If the mail client stays open, the mail store is skipped and retried about an hour later, indefinitely. Backblaze documentation advises closing mail applications at least once a day.
Where should password reset emails go?
To a separate mailbox at a different provider, used for nothing else. If reset messages arrive in the account you’re trying to recover, that’s a dependency loop and not a recovery address, and it only reveals itself on the day it breaks.
How long does it take to change recovery addresses on all your accounts?
Weeks, if you have the eighty or so accounts most people accumulate. Work in tiers instead of alphabetically. The registrar, hosting and mail providers carry most of the risk and can be done in an evening, financial accounts come next, and the long tail barely matters.
What is the fastest thing you can do to protect your email archive?
Name the three things in your inbox you couldn’t reconstruct from anywhere else, usually a tax document, a signed contract or old photographs, and download them today. That takes five minutes instead of becoming a backup project, and it covers most of what you’d grieve.

About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

19 comments
Was this useful?

Leave a comment