The Unsent Email
In late 2020, a systems analyst who asked to remain anonymous forwarded a message to several online security forums, believing it to be either a phishing attempt or a poorly executed prank.
The email had no sender information.
No address.
No routing data.
No originating IP.
According to the analyst, it appeared in his inbox as if it had always been there—no notification, no timestamp anomaly, just a new unread message threaded between two legitimate emails.
The subject line read:
RE: Still here
There was no previous conversation.
The body of the email was short.
You don’t remember the quiet part.
That’s normal.
Start with the attachments.
There were three files attached. All were empty text documents, each labeled with a date from 2006.
The analyst assumed corruption. He ran them through recovery tools, hex editors, and checksum verifiers. Nothing appeared.
Out of curiosity, he copied one file and changed the extension.
It opened.
Not as text, but as a timeline.
The file contained a list of timestamps, each exactly eleven minutes apart, spanning several hours on a single night in March 2006. Cross-referencing the date revealed nothing notable—no outages, no local events.
Until the analyst checked his own history.
He had lived in a different city then, but on that exact night, he had no digital footprint at all. No emails. No phone records. No browser activity.
A blank space.
The second file contained a floor plan.
It took him hours to recognize it as the apartment he lived in at the time—accurate down to the narrow closet he used for storage. A room he rarely entered was highlighted in gray.
The third file wouldn’t open.
The analyst attempted to trace the email’s origin. Server logs showed it bypassed normal routing entirely, appearing locally rather than arriving externally. No malware was detected. No evidence of intrusion.
He considered deleting it.
Instead, he replied.
Who is this?
The response arrived instantly.
Someone who noticed when you stopped.
At this point, skeptics point to dissociation, recovered memory, or an elaborate hoax requiring insider access. All plausible explanations.
They falter when examining the third attachment.
After the reply, the file unlocked.
Inside was an audio clip—silent at first glance. When visualized, it showed repeating troughs where sound should have been.
When amplified, the analyst heard his own breathing.
Slower than he remembered.
With long pauses between each inhale.
Eleven minutes apart.
The analyst stopped responding.
The emails continued anyway.
Each message referenced mundane details he hadn’t shared online—scratches on his desk, the hum of his refrigerator, the way his apartment sounded at night when everything else stopped.
The final email contained no text.
Only a subject line:
RE: Found you
He disconnected his internet that night.
The email was still there in the morning.
The account was closed shortly after. The analyst wiped his devices and moved. He no longer works in systems security.
The emails have not resurfaced.
What remains unexplained is how the original message appeared in his inbox before he opened the account it was sent to.
Or why, according to archived metadata, it was marked as read.
Eleven minutes before he first saw it.
3 responses to “Ep. 10: The Unsent Email”
Email headers don’t just fail to exist like that, so either details are being omitted or the story’s embellished. Still, the local-only delivery is a really odd touch.
Everyone’s asking who sent the emails, but not why they waited so long to follow up. “Someone who noticed when you stopped” implies this wasn’t the first time.
Dissociation and memory gaps can absolutely happen under stress, especially around the mid-2000s when logging wasn’t as complete. The personalization is what makes it harder to dismiss.