Email Infrastructure — Trivia & Interesting Facts¶
Surprising, historical, and little-known facts about email infrastructure.
The first email was sent in 1971, but nobody remembers what it said¶
Ray Tomlinson sent the first network email between two ARPANET machines in 1971 and chose the @ symbol to separate user from host. When asked later what the first email said, Tomlinson replied it was probably something like "QWERTYUIOP" — a test string. He chose @ because it was the least-used character on the keyboard and already meant "at" in English.
SMTP is from 1982 and is essentially unchanged¶
RFC 821, defining the Simple Mail Transfer Protocol, was published by Jon Postel in August 1982. The core protocol — HELO, MAIL FROM, RCPT TO, DATA — is still how email works today. ESMTP (RFC 5321, 2008) added extensions, but a mail server from 1985 could still theoretically participate in modern email delivery. Few internet protocols have shown this kind of longevity.
Sendmail once handled the majority of all internet email¶
Eric Allman wrote Sendmail at UC Berkeley in 1983, and by the mid-1990s it handled an estimated 70-80% of all internet email. Its configuration file (sendmail.cf) was so notoriously complex that the "Sendmail bat book" (O'Reilly, 1993) was over 1,000 pages long. The shift to Postfix, Exim, and cloud email services eventually dethroned it, but Sendmail's influence on email infrastructure is immeasurable.
SPF, DKIM, and DMARC took over 15 years to become standard¶
SPF was proposed in 2003, DKIM in 2007, and DMARC in 2012 — yet widespread adoption didn't happen until the mid-2020s. Google and Yahoo's February 2024 mandate requiring DMARC for bulk senders was the tipping point that finally forced adoption. Before these standards, anyone could send email claiming to be from any domain with zero authentication. The 15-year adoption gap shows how hard it is to change email infrastructure.
A misconfigured mail server can become an "open relay" and get blacklisted within hours¶
An open relay is a mail server that accepts and forwards email from any sender to any recipient, no authentication required. Spammers actively scan the internet for open relays. A freshly deployed, misconfigured Postfix server can appear on spam blacklists (RBLs) within 2-4 hours of going online. Getting delisted from major RBLs like Spamhaus can take days to weeks.
Microsoft Exchange has been the target of more zero-day attacks than almost any other software¶
The ProxyLogon (2021) and ProxyShell (2021) vulnerabilities in Microsoft Exchange were exploited by state-sponsored attackers to compromise an estimated 250,000+ servers worldwide. The March 2021 ProxyLogon attack was so severe that the US government authorized the FBI to remotely patch Exchange servers without their owners' permission — an unprecedented legal action.
Email bounces follow a surprisingly complex taxonomy¶
RFC 3463 defines 25 different enhanced mail status codes across five classes. A "5.1.1" means the mailbox doesn't exist, "4.7.1" means a temporary authentication failure, and "5.7.25" means a reverse DNS check failed. Most email administrators encounter only a handful of these codes, but large-scale email senders like Amazon SES track all of them to maintain deliverability scores.
Postfix was created as a direct response to Sendmail's complexity¶
Wietse Venema created Postfix (originally called VMailer, then IBM Secure Mailer) in 1998 at IBM's T.J. Watson Research Center. His explicit goal was to build a Sendmail replacement that was fast, secure, and easy to configure. Postfix's design of separate, unprivileged processes communicating through well-defined interfaces was revolutionary for mail servers and influenced the design of many later services.
Gmail's storage offer of 1 GB in 2004 was considered a joke¶
When Google announced Gmail on April 1, 2004, offering 1 GB of free storage, many people assumed it was an April Fools' prank. At the time, Yahoo Mail offered 4 MB and Hotmail offered 2 MB. Gmail's offer was 250x larger than the competition. The announcement fundamentally changed user expectations for email storage and forced every competitor to increase their limits.
MX record priority numbers are backwards from what you'd expect¶
In DNS MX records, a lower priority number means higher preference — the opposite of what most people intuitively expect. MX 10 is preferred over MX 20. This convention dates back to RFC 974 (1986) and has confused DNS administrators for nearly 40 years. The original intent was to allow finer-grained prioritization by inserting records between existing values.
Email headers can reveal the entire delivery path of a message¶
Each mail server that handles a message prepends a "Received:" header, creating a chain that shows every hop the message took from sender to recipient. Reading these headers bottom-to-top reconstructs the delivery path. Spammers often forge Received headers to obscure their origin, but the topmost header (added by the recipient's server) is generally trustworthy.
The email industry considers a bounce rate above 2% dangerous¶
Major email service providers like Gmail, Yahoo, and Microsoft monitor sender reputation metrics in real time. A bounce rate above 2%, a spam complaint rate above 0.1%, or a sudden volume spike can trigger automated throttling or blocking. Building and maintaining "IP warming" — gradually increasing send volume on a new IP — typically takes 4-6 weeks.