Some of the Web’s most useful backup systems were never intended to be backup systems at all.
A PDF disappears from a small organization’s website. The download page is gone. The domain later expires. Years afterward, somebody searching an old mailbox finds the same PDF attached to a message sent when the document was new.
The website failed. Email quietly kept a copy.
Attachments escape the fate of the original server
When a document is emailed as an attachment, another copy leaves the server that originally published it. That copy may end up in several inboxes, desktop mail archives, corporate retention systems, exported MBOX files, PST files, or personal backups.
That makes email an accidental distributed archive.
Professional archivists treat attachments as part of the record for exactly this reason. The Library of Congress recommends that email attachments remain in their original format. NARA’s transfer instructions for email with attachments likewise call for preserving the message structure and labels such as date, sender, recipients, subject, body, attachment filename, and related transmission information.
The attachment preserves the file. The message around it may preserve something just as important: why the file was sent.
Correspondence can restore provenance
Suppose an old attachment is named report.pdf. By itself, that filename says almost nothing.
The message may say, “Attached is the final version we posted this morning,” and carry a date, sender, organization, and thread discussing corrections. That surrounding correspondence can help establish when the document circulated and how people understood it at the time.
This is valuable when the original web page is gone because the email may provide provenance that a loose recovered file lacks.
But email evidence has limits.
An attachment may be a draft rather than the public version. The sender may have renamed it. Someone may have forwarded a modified copy. The email date proves when that message was sent, not necessarily when the underlying document was created. If several versions survive, checksums and internal document metadata can help determine whether they are actually identical.
Recovery does not automatically mean republication
There is also a privacy problem.
An attachment that once appeared publicly can often be republished without much mystery. An attachment found in private correspondence is different. The mailbox may contain personal information, unpublished drafts, addresses, internal comments, legal material, or information that was never intended for public distribution.
Preservation and publication are separate decisions.
Old email is therefore an unusually powerful archaeological layer. It can contain files that vanished from websites years ago and messages that explain what those files were. The Smithsonian’s email-preservation work treats messages and associated attachments as a collection-level preservation problem rather than disposable mail clutter. The best recovery work keeps the chain of evidence intact: preserve the original message, preserve the attachment separately, record hashes, document where it came from, and distinguish what is known from what is inferred.
Sometimes the last surviving copy of a public web document is sitting in a twenty-year-old inbox nobody thought to search.