2000: From ALL CAPS Flamewars to Corporate Style Guides: How Email Etiquette Evolved

Nobody teaches you how to write an email. There is no class in school, no chapter in an employee handbook (at least not until the early 2000s), no universal authority that decides whether “Best regards” is better than “Thanks” or whether a smiley face at the end of a work message is friendly or unprofessional. Email etiquette has always been learned the way social norms are usually learned: through observation, imitation, trial, error, and the occasional excruciating moment when you realize you did it wrong.

Over fifty years, those unwritten rules have shifted dramatically — from the anything-goes chaos of early internet culture to the polished corporate protocols of the modern workplace, with a long, awkward adolescence in between. The story of email etiquette is the story of millions of people figuring out, in real time, how to communicate in a medium that had no precedent.

The Simple Version: When email was brand new, people made up the rules as they went along. Some people typed IN ALL CAPS (which felt like yelling), some wrote novels when a sentence would do, and some forwarded every joke and chain letter to everyone they knew. Over time, workplaces created email policies, people learned what was annoying, and a rough set of email manners emerged. But we still argue about things like when to use “Reply All” and whether it is okay to end an email with just “K.”

The Wild West: Email Before Rules (1970s-1993)

In the earliest days of email on ARPANET and its academic successors, there were no etiquette norms because there was barely a culture to have norms in. The user base consisted almost entirely of computer scientists, engineers, and researchers who were inventing the medium as they used it. Messages were terse, technical, and functional. Nobody worried about tone because everyone reading the messages shared the same professional context.

The first hint that email needed social conventions came not from email itself but from Usenet, the distributed discussion system that emerged in the early 1980s. Usenet newsgroups developed the earliest recognizable “netiquette” norms — don’t type in ALL CAPS (it looks like shouting), don’t post off-topic messages, don’t “flame” (attack someone personally), quote the relevant portion of a message when replying. These conventions migrated naturally to email because the user populations overlapped almost completely.

The ALL CAPS norm is worth pausing on because it became perhaps the single most universal rule of digital communication. In a text-only medium, capitalization was one of the few tools available for emphasis. But because ALL CAPS text is visually aggressive — the uniform letter height removes the visual rhythm that makes mixed-case text readable — early internet users interpreted it as yelling. That interpretation stuck. Three decades later, typing in ALL CAPS in a work email remains one of the fastest ways to make colleagues think you are either furious or technologically illiterate.

RFC 1855: The First Official Guide (1995)

In October 1995, the Internet Engineering Task Force published RFC 1855, titled “Netiquette Guidelines.” Authored by Sally Hambridge of Intel Corporation, it was the first formal attempt to codify online communication norms, and its email section reads like a time capsule of mid-1990s internet culture.

The document advised users to check their email at least once a day. It warned against sending large attachments. It recommended including a signature block of no more than four lines. It advised against typing in ALL CAPS. It counseled brevity: “try to keep messages concise and to the point.” It warned against sending “chain letters” via email and noted that such practices were often violations of acceptable use policies.

What RFC 1855 could not anticipate was the scale of the coming transformation. When it was published, global internet users numbered roughly 16 million, email was still primarily a tool of the technical community and academia, and the AOL mass-market explosion was just beginning. The rules it proposed were sensible for a small, relatively homogeneous community. They would need significant adaptation when hundreds of millions of new users arrived.

The AOL Influx and the Flame Wars (1995-2000)

When America Online opened its gates to the internet in the mid-1990s, millions of people who had never used email suddenly had email addresses. They had no exposure to the netiquette conventions that had developed on Usenet and in academic circles. They brought their own communication instincts, shaped by telephone calls, handwritten letters, and face-to-face conversation, and applied them — often badly — to the new medium.

The result was a sustained cultural collision. New users wrote emails in ALL CAPS because they thought it was easier to read. They forwarded everything — jokes, chain letters, hoaxes, and virus warnings — to everyone in their address book. They composed emails that were either five words or five pages, with nothing in between. They hit “Reply All” when they meant “Reply.” They did not use subject lines, or used subject lines like “HI” or “IMPORTANT READ THIS NOW.”

The seasoned internet users were appalled. The culture clash between the existing community and the AOL newcomers — dismissively called the “Eternal September” because the influx of naive users never ended — generated some of the first widespread discussions about email behavior. Flame wars erupted: extended, hostile exchanges where participants escalated in anger and personal attack, fueled by the disinhibiting effects of text-based communication. Without tone of voice, facial expressions, or social consequences, people wrote things in emails they would never say in person.

The Corporate Awakening (2000-2008)

By the early 2000s, email had become the dominant medium of professional communication, and corporations began to realize they had a problem. Employees were writing emails that created legal liability, generating HR complaints, wasting colleagues’ time with unnecessary CCs, and generally communicating in ways that reflected poorly on the organization. The corporate email policy was born.

These policies ranged from common sense to absurdly detailed. The common sense end included guidelines like “don’t send confidential information to personal email accounts” and “don’t use company email for personal matters.” The detailed end attempted to legislate tone, format, and even vocabulary. Some organizations mandated formal salutations (“Dear Mr./Ms.”), prohibited abbreviations, required full sentences, and specified acceptable sign-offs.

The corporate email training industry emerged during this period. Consulting firms offered workshops on “effective email communication.” Books with titles like “Email Etiquette” and “Send: The Essential Guide to Email for Office and Home” appeared in airport bookshops. The underlying message was consistent: email is a professional tool, treat it with the same care you would give a business letter.

The advice that crystallized during this era became something close to a consensus standard for professional email: use a clear subject line, keep the message concise, address the recipient by name, state the purpose in the first sentence, use proper grammar and spelling, avoid ALL CAPS, be cautious with humor (it doesn’t translate well in text), use CC judiciously, respond within 24 hours, and end with a professional sign-off.

The CrackBerry Era and Always-On Email (2005-2010)

The BlackBerry changed email etiquette by changing when and where people read email. Before mobile email, there was a natural rhythm: you wrote emails at your desk during business hours, and you were not expected to respond evenings or weekends. The BlackBerry — and later the iPhone — destroyed that boundary.

Suddenly, emails arrived at dinner, on vacation, in bed. The etiquette question shifted from “how do I write a good email?” to “when am I obligated to respond?” Some organizations developed explicit policies — no work email after 7 PM, no email on weekends. France eventually codified this into law with the “right to disconnect” legislation in 2017. But in most workplaces, the norm settled into an uncomfortable ambiguity: you were not technically required to respond at 10 PM, but you noticed that the people who got promoted usually did.

Mobile email also changed the format of messages. Typing on a BlackBerry keyboard — or, worse, on an iPhone touchscreen — was physically slower and more error-prone than typing on a desktop keyboard. Emails sent from mobile devices were shorter, more informal, and more prone to typos. The “Sent from my iPhone” signature became a culturally loaded signal: it simultaneously apologized for brevity and advertised that the sender was important enough to be responding on the go.

The Emoji Question (2010-2020)

As smartphones made communication increasingly casual, a new etiquette question emerged: are emoji appropriate in professional email? The debate was fierce and remains unresolved.

The anti-emoji camp argued that professional communication required professionalism, and that smiley faces, thumbs-ups, and winking faces undermined credibility. A 2017 study by researchers at Ben-Gurion University of the Negev appeared to confirm this: participants who received initial work emails containing smiley face emoticons rated the sender as less competent than those who received the same email without them. The study was widely cited by etiquette consultants and anyone who wanted a peer-reviewed reason to dislike email emoji.

The pro-emoji camp countered that digital communication lacks the tonal cues of spoken conversation, and that emoji fill a crucial gap. “Sounds good” and “Sounds good!” and “Sounds good :)” convey three subtly different emotional tones. Without some form of tonal signaling, text-based communication is prone to misinterpretation — a problem that has generated countless workplace conflicts since email’s earliest days.

The practical resolution, insofar as one exists, is contextual. Internal communication between colleagues who know each other well tolerates more informality than external communication with clients or partners. Established relationships tolerate more informality than first-contact messages. Creative industries tolerate more informality than legal or financial firms. The emoji question did not produce a universal answer because there is no universal professional culture.

The Modern Era: Brevity, Async, and the Death of Formality (2020-Present)

The COVID-19 pandemic accelerated a trend that was already underway: the collapse of formal email conventions. When everyone was working from home, communicating exclusively through screens, and managing unprecedented levels of stress and uncertainty, the distinction between “professional email” and “casual message” blurred significantly. Emails got shorter. Sign-offs got more casual — “Best,” “Thanks,” “Cheers,” “—J.” Salutations became optional. Sentences became fragments.

The rise of Slack, Microsoft Teams, and other workplace messaging tools also influenced email etiquette by absorbing the quick, informal communication that used to happen via email. When internal chat handles the “quick question” and “can you look at this?” messages, email increasingly carries only the communication that is too formal, too complex, or too external for chat. This filtering effect has made email, paradoxically, both more formal (because the casual stuff moved elsewhere) and less formal (because the broader cultural trend is toward informality in all digital communication).

The current state of email etiquette is a patchwork of old norms, new conventions, and persistent ambiguity. Some things are universally agreed upon: don’t type in ALL CAPS, don’t Reply All to company-wide emails, don’t send one-word responses to detailed questions. But many questions remain actively contested: Is “Hey” an acceptable salutation in a work email? Should you use exclamation points? How quickly do you need to respond? Is it acceptable to email on weekends? Can you use GIFs? Should your email signature include your pronouns? Your LinkedIn? An inspirational quote?

The Etiquette That Never Changes

Beneath all the shifting norms and generational debates, a few email etiquette principles have remained constant since the medium’s earliest days. Write a subject line that tells the recipient what the email is about. Be as brief as the content allows. Proofread before you send. Don’t write anything in an email you would not want forwarded to the entire company. Think before you CC.

These principles endure because they are not really about email at all. They are about respect for the recipient’s time and attention — a principle that applies to every form of communication, from handwritten letters to carrier pigeons. The medium changes. The need to communicate clearly and considerately does not.

For email marketers, the history of email etiquette carries a direct practical lesson. The norms that govern person-to-person email inevitably shape how recipients perceive marketing email. Subject lines in ALL CAPS trigger the same negative reaction in a promotional email that they trigger in a personal one. Excessive length, unclear purpose, and sloppy formatting communicate the same thing in a newsletter that they communicate in an office email: the sender does not respect the reader’s time. The most effective marketing emails have always been the ones that follow the same etiquette principles that govern good communication of any kind.

Infographic

Share this visual summary. Right-click to save.

Frequently Asked Questions

Why is typing in ALL CAPS considered rude in email?

Typing in ALL CAPS has been considered 'shouting' since the earliest days of online communication. The convention was established in Usenet newsgroups and early internet culture during the 1980s, where bandwidth and screen real estate were limited. ALL CAPS text is harder to read because it removes the visual shape variation that mixed-case text provides, and early internet users adopted the social norm that capitalized text indicated anger or aggression. The convention migrated to email as the user bases overlapped.

What were the original netiquette rules for email?

The earliest codified netiquette rules appeared in RFC 1855, published in October 1995 by the Internet Engineering Task Force. Key rules included: don't type in ALL CAPS, keep messages concise, use descriptive subject lines, don't send large attachments without warning, quote relevant portions of the original message when replying, include a signature block with contact information, and don't send chain letters. Many of these rules remain relevant thirty years later.

Is it appropriate to use emoji in professional emails?

This remains one of the most debated email etiquette questions. Research from 2017 by Ben-Gurion University found that smiley face emoticons in initial work emails actually decreased perceptions of competence. However, more recent studies suggest that once a professional relationship is established, judicious emoji use can convey warmth and reduce ambiguity. The general consensus is that emoji are acceptable in internal, informal communications but should be avoided in first-contact emails, client-facing messages, and formal business correspondence.