Scribd
Upload
31 views4 pages

Understanding Email Architecture and Protocols

Electronic mail (e-mail) enables users to exchange messages through a client-server architecture involving mail servers that manage message delivery. The process includes components like User Agents (UAs) for composing and reading messages, Message Transfer Agents (MTAs) for transferring messages, and Message Access Agents (MAAs) for retrieving them. Various transport-layer protocols, such as UDP, TCP, and SCTP, facilitate communication, each with distinct characteristics suited for different application requirements.

Uploaded by

Niveditha Prakash
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
31 views4 pages

Understanding Email Architecture and Protocols

Electronic mail (e-mail) enables users to exchange messages through a client-server architecture involving mail servers that manage message delivery. The process includes components like User Agents (UAs) for composing and reading messages, Message Transfer Agents (MTAs) for transferring messages, and Message Access Agents (MAAs) for retrieving them. Various transport-layer protocols, such as UDP, TCP, and SCTP, facilitate communication, each with distinct characteristics suited for different application requirements.

Uploaded by

Niveditha Prakash
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Electronic Mail

 Electronic mail (or e-mail) allows users to exchange messages.


 The nature of this application, however, is different from other applications discussed
so far.
 In an application such as HTTP or FTP, the server program is running all the time,
waiting for a request from a client.
 When the request arrives, the server provides the service. There is a request and there
is a response.
 In the case of electronic mail, the situation is different. First, e-mail is considered a
one-way transaction.
 When Alice sends an email to Bob, she may expect a response, but this is not a
mandate. Bob may or may not respond. If he does respond, it is another one-way
transaction.
 Second, it is neither feasible nor logical for Bob to run a server program and wait until
someone sends an e-mail to him. Bob may turn off his computer when he is not using
it.
 This means that the idea of client/server programming should be implemented in
another way: using some intermediate computers (servers).
 The users run only client programs when they want and the intermediate servers apply
the client/server paradigm.

Architecture:

 E-mail communication involves the sender and receiver connected via LAN or
WAN to two mail servers, where each mail server manages the exchange of
messages.
 Each user has a dedicated mailbox on the mail server, stored securely on the
server's hard drive with access restricted to the mailbox owner.
 The administrator creates a queue or spool on the mail server to temporarily store
messages waiting to be sent to the recipient.
 The sender uses a user agent (UA) to compose and send a message, which is then
passed to the sender’s mail server for processing and delivery.
 The sender’s mail server uses a message transfer agent (MTA) to forward the
message to the recipient’s mail server over the Internet.
 The MTA communication involves two components: the sender’s mail server acts
as the client, and the recipient’s mail server acts as the server.
 The recipient retrieves the message using a message access agent (MAA) and
reads it via a user agent (UA) on their device.
 The MTA uses a push model to transfer messages to the server, while the MAA
employs a pull model to retrieve messages for the recipient.
 Direct communication with the MTA server is not feasible for the recipient as it
would require the recipient's system to remain online constantly, which is
impractical.
 The architecture ensures asynchronous communication between the sender and
receiver using multiple servers and client-server applications to facilitate reliable
message transfer.

User Agent:

 The User Agent (UA) is the first component of an e-mail system, designed to simplify
the process of sending and receiving messages for users.
 A UA is a software package that allows users to compose, read, reply to, and forward
messages, as well as manage local mailboxes on their computers.
 UAs can be of two types:
Command-Driven: Operates with single-character commands, used in early e-mail
systems (e.g., mail, pine, elm).
GUI-Based: Uses graphical interfaces like icons and windows for ease of interaction
(e.g., Eudora, Outlook).
 To send mail, the UA creates an e-mail with two components:
Envelope: Contains sender and recipient addresses.
Message: Includes the header (e.g., subject, sender) and the body (the actual
message).
 For receiving mail, the UA notifies the user of new messages and displays a summary
of key details (e.g., sender, subject, time). The user can select and view any message.
 E-mail addresses consist of a local part (user's mailbox name) and a domain name
(mail server name), separated by @, ensuring unique identification.
 UAs support mailing lists, where one alias represents multiple recipients. The
system prepares separate messages for each recipient in the list.
 Mailing lists and group lists allow efficient communication with multiple recipients by
using a single alias to represent all the addresses.

Message Transfer Agent:

 E-mail communication relies on three client-server paradigms: two involving


Message Transfer Agents (MTAs) and one involving a Message Access Agent
(MAA).
 The Simple Mail Transfer Protocol (SMTP) defines the interaction between MTA
clients and servers, enabling the transfer of messages.
 SMTP is used twice in the e-mail process: first between the sender and the sender’s
mail server, and then between the two mail servers.
 SMTP governs how commands (from the client) and responses (from the server) are
exchanged to ensure successful message delivery.
 Commands in SMTP are keywords with optional arguments, sent by the client to the
server, with a standardized format.
 Responses from the server are three-digit codes, often accompanied by additional
text, indicating the status of the command execution.
 SMTP commands and responses are terminated using a two-character end-of-line
token (carriage return and line feed).
 SMTP facilitates a robust mechanism for reliable message transfer, though another
protocol (e.g., POP3 or IMAP) is needed for message retrieval by the receiver.
Services Provided by Transport Layer with different protocols:

 The transport layer provides communication services to application processes since


there is no physical communication at the application layer.

 The TCP/IP suite includes three common transport-layer protocols: UDP, TCP, and
SCTP.

 These protocols are chosen based on the application's specific requirements for
reliability, speed, and message handling.

 Applications use transport-layer services to facilitate data transfer between two


processes on different devices.

 UDP is connectionless and message-oriented, suitable for simple, fast communication.

 TCP is connection-oriented and byte-stream-oriented, ensuring reliable


communication with flow and congestion control.

 SCTP combines features of both UDP and TCP, offering reliable and message-
oriented communication with multi-streaming capabilities.

 The choice of protocol directly impacts the application's communication capabilities


and performance.

UDP Protocol:

1. UDP (User Datagram Protocol) is a connectionless protocol, meaning it does not


establish a logical connection between the sender and receiver before transmitting
data.
2. It provides an unreliable datagram service, as it does not guarantee the delivery of
messages or retransmit lost or corrupted data.
3. Each message in UDP is treated as an independent datagram without any relationship
to previous or subsequent messages.
4. It does not use flow control or error correction mechanisms, relying on simplicity and
speed.
5. UDP is a message-oriented protocol, preserving the boundaries of messages during
transmission.
6. It is suitable for applications that prioritize speed over reliability, such as real-time
applications like video streaming, gaming, and DNS queries.

`1TCP Protocol :

1. TCP (Transmission Control Protocol) is a connection-oriented protocol, requiring a


handshake process to establish a logical connection between the sender and receiver.
2. It ensures reliable communication by sequencing data and retransmitting lost or
corrupted packets.
3. TCP uses flow control to manage the rate of data transmission between sender and
receiver, preventing buffer overflow.
4. It incorporates congestion control meanisms to avoid overwhelming the network
during high traffic.
5. Data is transmitted as a byte stream, meaning boundaries between messages are not
preserved.
6. TCP’s handshaking phase establishes parameters such as buffer size and data packet
size for efficient communication.
7. It is suitable for applications requiring reliability and large data transfers, such as file
downloads, e-mail, and web browsing.

SCTP Protocol:

1. SCTP (Stream Control Transmission Protocol) combines features of both TCP and
UDP, providing reliable, connection-oriented, and message-oriented communication.
2. It supports multi-streaming, enabling multiple independent streams within a single
connection to prevent head-of-line blocking.
3. It uses a four-way handshake for connection establishment, providing enhanced
security compared to TCP.
4. SCTP is suitable for applications requiring high reliability and real-time
communication, such as VoIP and telecommunications signaling.
5. It provides congestion control and flow control, similar to TCP, for efficient data
transmission.
6. SCTP is designed to remain connected even if one network path fails, ensuring
continuous communication.

Common questions

Powered by AI

Maintaining a server program constantly running on Bob's system is impractical due to the need for continuous power and internet connectivity, which is not feasible for typical user environments. This challenge is addressed by offloading server responsibilities to intermediate mail servers, which store and manage message delivery. This design allows users to operate only when needed and ensures efficient and reliable communication through server-side management .

SMTP facilitates email communication by defining the interaction between MTA clients and servers, using commands and responses to ensure the transfer of messages between servers. However, SMTP is primarily designed for message sending and thus does not handle the retrieval process from a server to a user's device. This necessitates additional protocols like POP3 or IMAP, which efficiently manage the retrieval process, allowing users to download their emails from the recipient's mail server .

UDP differs from TCP in that it is connectionless and provides an unreliable datagram service, prioritizing speed over reliability. It does not guarantee message delivery or retransmit lost data, making it suitable for applications requiring fast, lightweight communication like video streaming and gaming. Conversely, TCP is connection-oriented, ensures message reliability through sequencing and retransmission, and is used when reliability is crucial, such as in file downloads and email. UDP is preferred in scenarios where low latency is more important than data integrity .

The MTA plays a crucial role in routing and delivering emails between servers in the email communication process. It uses the push model to transfer messages, acting as the client or server at different times. In contrast, the MAA facilitates message retrieval from a mail server using the pull model, allowing users to access messages via a User Agent (UA). MTAs are responsible for delivery, whereas MAAs are used for accessing received emails .

Intermediate servers are crucial in email architecture because they facilitate the client/server programming model required for asynchronous email communication. Since it is impractical for the recipient to run a server program and stay constantly online, intermediate servers handle message storage and forwarding. They allow the sender and receiver to connect via LAN or WAN to mail servers that manage message exchanges, ensuring reliable delivery even when the recipient's system is offline .

User agents (UAs) in email systems come in two types: Command-Driven and GUI-Based. Command-Driven UAs operate through single-character commands, typical in early email systems like 'mail' and 'pine,' offering a text-based interface. GUI-Based UAs make use of graphical interfaces with icons and windows, exemplified by software like Eudora and Outlook, enhancing user interaction with visual elements and broader functionality .

SMTP handles server-client interactions by exchanging well-defined commands and responses that ensure messages are sent from the client's local server to the recipient's server. Each SMTP command has standardized formats and responses, indicating the command execution status. However, SMTP is not designed for message retrieval; additional protocols like POP3 or IMAP are necessary for users to download emails from the recipient server to their devices .

The email communication design ensures security and privacy by utilizing MTAs to handle messages over secure connections and MAAs to provide access only to authenticated users. Mail servers store messages securely, ensuring only the mailbox owner can access them, and MTAs facilitate encrypted transmission where possible. This layered approach using both MTAs and MAAs reduces the risk of unauthorized access and maintains message confidentiality .

The architecture of email communication ensures asynchronous communication through the use of intermediate mail servers that store messages until they can be delivered to the recipient. This eliminates the need for the recipient to be online constantly and provides flexibility for users to access messages at their convenience. The asynchronous model benefits users by reducing dependency on others' availability and improves the system's efficiency in managing network resources .

SCTP combines features of both TCP and UDP with its reliable, connection-oriented, yet message-oriented communication. It supports multi-streaming, allowing multiple independent streams within a single connection, and uses a four-way handshake for enhanced security. SCTP is beneficial for applications requiring high reliability and real-time communication, such as VoIP and telecommunications signaling, because it can maintain connections even in case of network path failures .

You might also like