Data Recovery Case File · Email Archives · The Mirror Remembers

When the provider loses it and you still have it: a decade's email archive rebuilt from the local store the server failure never touched

His enquiry began with fair warning — "my story is a bit long and complicated" — and delivered the most instructive email case in this archive. The archive: more than ten years of correspondence, over 100,000 messages, sorted into hundreds of folders, held in mail accounts with his internet provider. The disaster: the provider "suffered a catastrophic server failure and lost about 10% of all my messages. They were neither willing nor able to recover this loss" — an apology, an assurance, and nothing back. The aftermath at his desk: his Linux mail client — an open-source program he'd used for years — now showing scrambled message numbering in the archive folders since the crash, the local view unsettled by the server's amputation. His question was whether anything could be done about a loss that had happened on someone else's machine. The answer is this page's whole thesis: his machine had been quietly keeping a copy all along.

The decode: IMAP is a mirror — and why the client's confusion was the treasure's marker

The architecture that saved the decade: IMAP email lives on the provider's server as the master copy — but a desktop client used daily for years does not merely view that server: it mirrors it, downloading messages into a local store so folders open instantly and mail works offline. His client's store, built across a decade of use, held its own copy of the archive as it stood — including, crucially, the ten percent the server failure deleted: messages the provider's disks lost but his own disk had faithfully mirrored long before the crash. The provider was right that they couldn't recover the loss; the loss simply wasn't only theirs to hold. The client's scrambled numbering, decoded as a signpost: after the server's amputation, his mail program was caught between two truths — a local store remembering messages the server now denied — and its unsettled folder listings were the visible seam between the surviving mirror and the damaged master. The vital part was what he didn't do about it: no forced full resync (which teaches the local store to match the server — i.e., to delete its copies of the lost messages), no cache clearing, no folder "repairs." A resync at that moment would have completed the provider's failure on his own machine; his restraint left the mirror intact. The doctrine, for every long-archive keeper: when a provider loses mail, the local store becomes the sole surviving copy — freeze the client, work offline, and treat that cache as the patient it now is.

The recovery — the mirror excavated, the archive made whole

The client's local mail store was imaged and excavated offline — the program's message files read directly, folder by folder through the hundreds, each message an individual file in the store's plain, well-documented format — and the reconciliation ran against the provider's surviving server side: the local mirror's contents compared to the post-crash master, and the lost tenth identified and extracted — thousands of messages, spanning the decade, present in his own store exactly as the mirror had kept them. The rebuilt archive was assembled whole: the server's survivors and the cache's rescues merged, de-duplicated, and restored to his folder structure, verified by sampling across years and folders — then delivered in standard, portable mail formats on new media in duplicate, importable to any client and any provider, with the report closing on the arrangement a decade's correspondence deserves: the archive now exists in three places — the provider, his machine, and a scheduled export — because the mirror saved it once, and mirrors shouldn't have to be lucky twice.

Outcome

The lost tenth restored from his own machine, the decade made whole — and the filings every long-archive keeper needs before their provider's bad day. Know that IMAP mirrors: a daily-driven desktop client holds a local copy of your mail — which means a server-side loss is survivable if the mirror is frozen in time: no resyncs, no cache clears, no reinstalls, the moment a provider announces loss. Treat provider assurances as scope statements: "we cannot recover it" describes their disks, not yours. And export deliberately: a scheduled archive export in portable formats turns the lucky mirror into a real backup — a decade of correspondence should never again depend on one company's server room or one laptop's cache. The provider lost ten percent and apologised. His own machine had been keeping the receipts for ten years — and gave every one of them back.

Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.