2.3 Email
Introduction to Email as a Cultural Application
Overview of Email's Historical Context
- Email has been around since 1972 and is deeply embedded in culture, highlighted by the movie "You've Got Mail" from 1998.
- The discussion will focus on email infrastructure, including user agents (mail clients), email servers, messages, and message queues.
Components of Email Infrastructure
- The three main components of email are:
- User agent (mail client)
- Email servers (similar to HTTP servers)
- SMTP protocol (Simple Mail Transfer Protocol)
User Agent Functionality
- The user agent allows users to compose, edit, and read emails; it interacts with the server for storing messages.
- Each user's mailbox contains incoming messages and a queue for outgoing messages waiting to be sent.
Understanding the SMTP Protocol
Role of SMTP in Email Transmission
- SMTP is responsible for transferring messages between user agents and mail servers using a client-server model.
Example of Sending an Email
- An example illustrates Alice sending an email to Bob:
- Alice composes her message using her mail client.
- Upon hitting send, her client contacts her email server via SMTP.
Steps in Message Transfer
TCP Connection Establishment
- After Alice's message reaches her server, it establishes a TCP connection with Bob's server to transfer the message.
Message Delivery Process
- Alice’s server sends the message over TCP to Bob’s SMTP server which then places it into Bob’s mailbox for future retrieval.
Technical Details of SMTP
Handshaking Protocol in SMTP
- RFC 5321 defines how SMTP operates over TCP; port 25 is standard for connecting to an SMTP server.
Phases of Message Transfer
- There are three phases during message transfer:
- Handshake initiation with a "220" response from the receiving server.
- Exchange greetings between servers ("hello").
- Finalizing the transfer with termination signals.
Interaction Between Servers
Example Interaction Between Servers
- A simple interaction shows how Alice's email server communicates with Bob's:
- Initial greeting responses establish connection before transferring actual message data.
Observations on SMTP vs. HTTP
Key Differences Between Protocol Types
- Unlike HTTP which pulls data from servers, SMTP pushes messages from clients or mail servers.
Characteristics of Messages in SMTP
- Messages are human-readable ASCII text encoded format.
- Status codes exist similar to those in HTTP but differ in application context.
Structure of Mail Messages
Format Specifications
- RFC 2822 outlines syntax for email messages including headers (To, From, Subject).
- Body follows after a blank line and must be encoded in ASCII format.
Retrieving Emails at Destination Server
Accessing Emails Using IMAP
- IMAP (Internet Message Access Protocol), defined in RFC 3501, is commonly used for retrieving emails from destination servers.
Summary of Discussion Points
Recap on Email Infrastructure and Protocol
- Reviewed components like mail clients/servers and discussed the functioning of the Simple Mail Transfer Protocol as an example of client-server communication.
Transitioning Topics
Upcoming Topic Preview
- Next section will cover DNS protocol which differs significantly from both SMTP and HTTP protocols.
Turn any video into a summary like this
YouTube links, meetings, lectures. With transcripts, search, and chat.





