What Is Electronic Mail?

Electronic mail, universally abbreviated as email, is an asynchronous digital messaging system that allows users to compose, send, receive, and store text-based and multimedia messages through networked computer systems. An email message travels from a sender's mail client through one or more mail transfer agents to the recipient's mailbox server, where it waits until the recipient's client retrieves it. Unlike real-time communication systems such as telephone or instant messaging, email does not require both parties to be connected simultaneously, making it well-suited for communication across time zones and organizational boundaries.

Email traces its origins to the ARPANET era of the early 1970s, when Ray Tomlinson at BBN Technologies adapted existing message-passing programs to route messages between users on different host computers, introducing the now-ubiquitous format of user@host for addressing. From that experimental beginning, email grew into one of the most widely used communication systems in the world, now transmitting hundreds of billions of messages daily across an infrastructure governed by open, publicly documented protocols.

Protocol Architecture

The email infrastructure relies on a layered set of protocols that divide the work of sending, routing, and retrieving messages. The Simple Mail Transfer Protocol (SMTP), first standardized as RFC 821 in 1982 and updated by RFC 5321 in 2008, handles the transmission of messages between mail servers. When a sender's client submits a message, it connects to an SMTP server, which performs DNS lookups on the recipient domain's mail exchange (MX) records to find the next hop and relays the message along until it reaches the destination server. Retrieval protocols, Post Office Protocol version 3 (POP3) and Internet Message Access Protocol (IMAP), govern how mail clients download messages from servers to the user's device. IMAP, defined in RFC 9051, supports folder management and selective synchronization, making it the preferred protocol when users access a mailbox from multiple devices.

Message Format and MIME

The structure of an email message is defined by RFC 5322, which specifies the syntax of header fields such as From, To, Subject, Date, and Message-ID, along with the rules for encoding the message body. Plain text alone was sufficient for the original mail system, but the Multipurpose Internet Mail Extensions (MIME) standard extended email to support rich content: formatted text, images, audio, video, and binary file attachments. The MIME standard, defined across RFC 2045 through 2049, achieves this by encoding non-ASCII content as base64 or quoted-printable text within the message body and by allowing multipart message structures that carry several content types together. These standards ensure that messages composed on one mail client display correctly when rendered on a different client from a different vendor.

Security and Spam Filtering

The original email protocol assumed a trusted network and performed no sender authentication, a design choice that created an enduring spam and phishing problem. Modern email infrastructure addresses this through authentication standards layered onto SMTP: Sender Policy Framework (SPF) allows domain owners to specify which IP addresses may send mail on their behalf; DomainKeys Identified Mail (DKIM) adds a cryptographic signature to outgoing messages that receiving servers can verify; and Domain-based Message Authentication, Reporting, and Conformance (DMARC) ties SPF and DKIM together into a policy that defines how receivers should handle unauthenticated messages. The IETF DMARC standard describes how these mechanisms combine to reduce impersonation attacks. Spam filtering systems apply machine learning classifiers and reputation databases to block unsolicited bulk mail before it reaches users' inboxes.

Applications

Electronic mail has applications across a wide range of personal and professional contexts, including:

• Business and organizational communication between individuals and teams
• Customer service and transactional notifications from organizations
• Marketing campaigns and subscription newsletters
• Automated system alerts and operational notifications from software platforms
• Academic and research communication and manuscript submission workflows
• Legal and administrative record-keeping where written documentation is required