Scribd
Upload
13 views51 pages

Lecture 9

The document discusses the architecture and components of electronic mail (e-mail), including user agents, message transfer agents, and message access agents. It also covers file transfer protocols like FTP and the Hypertext Transfer Protocol (HTTP), detailing their functions and usage. Additionally, it includes a computer science assignment related to SMTP, POP, IMAP, FTP, and HTTP.

Uploaded by

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

Lecture 9

The document discusses the architecture and components of electronic mail (e-mail), including user agents, message transfer agents, and message access agents. It also covers file transfer protocols like FTP and the Hypertext Transfer Protocol (HTTP), detailing their functions and usage. Additionally, it includes a computer science assignment related to SMTP, POP, IMAP, FTP, and HTTP.

Uploaded by

samarjeetkaur027
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 51

ELECTRONIC MAIL

One of the most popular Internet services is electronic


mail (e-mail). The designers of the Internet probably
never imagined the popularity of this application
program. Its architecture consists of several
components that we discuss in this chapter.

Topics discussed in this section:


Architecture
User Agent
Message Transfer Agent: SMTP
Message Access Agent: POP and IMAP
Web-Based Mail
26.1
First scenario in electronic mail

26.2
Note

When the sender and the receiver of an


e-mail are on the same system,
we need only two user agents.

26.3
Second scenario in electronic mail

26.4
Note

When the sender and the receiver of an


e-mail are on different systems, we
need two UAs and a pair of
MTAs (client and server).

26.5
Third scenario in electronic mail

26.6
Note

When the sender is connected to the


mail server via a LAN or a WAN,
we need two UAs and two pairs
of MTAs (client and server).

26.7
Fourth scenario in electronic mail

26.8
Push versus pull in electronic email

26.9
Note

When both sender and receiver are


connected to the mail server via
a LAN or a WAN, we need two
UAs, two pairs of MTAs
and a pair of MAAs.
This is the most common situation
today.

26.10
Services of user agent

26.11
Note

Some examples of command-driven


user agents are mail, pine,
and elm.

26.12
Note

Some examples of GUI-based user


agents are Eudora, Outlook, and
Netscape.

26.13
Format of an e-mail

26.14
E-mail address

26.15
MIME (Multipurpose Internet mail Extension)

26.16
MIME header

26.17
Data types and subtypes in MIME

26.18
Content-transfer-encoding

26.19
SMTP range

26.20
Commands and responses

26.21
Command format

26.22
POP3 and IMAP4 (Internet mail access protocol)

26.23
The exchange of commands and responses in POP3

26.24
FILE TRANSFER

Transferring files from one computer to another is one


of the most common tasks expected from a networking
or internetworking environment. As a matter of fact,
the greatest volume of data exchange in the Internet
today is due to file transfer.

Topics discussed in this section:


File Transfer Protocol (FTP)
Anonymous FTP

26.25
Note

FTP uses the services of TCP. It needs


two TCP connections.

The well-known port 21 is used for the


control connection and the well-known
port 20 for the data connection.

26.26
Figure FTP

26.27
Figure Using the control connection

26.28
Figure 26.23 Using the data connection

26.29
27-3 HTTP

The Hypertext Transfer Protocol (HTTP) is a protocol


used mainly to access data on the World Wide Web.
HTTP functions as a combination of FTP and SMTP.

Topics discussed in this section:


HTTP Transaction
Persistent Versus Nonpersistent Connection

27.30
Note

HTTP uses the services of TCP on well-


known port 80.

27.31
Figure 27.12 HTTP transaction

27.32
Figure 27.13 Request and response messages

27.33
Figure 27.14 Request and status lines

27.34
Table 27.1 Methods

27.35
Table 27.2 Status codes

27.36
Table 27.2 Status codes (continued)

27.37
Figure 27.15 Header format

27.38
Note

A header line belong to one of four categories:


1. General Header
2. Request Header
3. Response Header
4. Entity Header

27.39
Table 27.3 General headers

27.40
Table 27.4 Request headers

27.41
Table 27.5 Response headers

27.42
Table 27.6 Entity headers

27.43
Example 27.1

This example retrieves a document. We use the GET


method to retrieve an image with the path /usr/bin/image1.
The request line shows the method (GET), the URL, and
the HTTP version (1.1). The header has two lines that
show that the client can accept images in the GIF or
JPEG format. The request does not have a body. The
response message contains the status line and four lines
of header. The header lines define the date, server, MIME
version, and length of the document. The body of the
document follows the header (see Figure 27.16).

27.44
Figure 27.16 Example 27.1

27.45
Example 27.2

In this example, the client wants to send data to the


server. We use the POST method. The request line shows
the method (POST), URL, and HTTP version (1.1). There
are four lines of headers. The request body contains the
input information. The response message contains the
status line and four lines of headers. The created
document, which is a CGI document, is included as the
body (see Figure 27.17).

27.46
Figure 27.17 Example 27.2

27.47
Example 27.3

HTTP uses ASCII characters. A client can directly


connect to a server using TELNET, which logs into port
80 (see next slide). The next three lines show that the
connection is successful. We then type three lines. The
first shows the request line (GET method), the second is
the header (defining the host), the third is a blank,
terminating the request. The server response is seven
lines starting with the status line. The blank line at the
end terminates the server response. The file of 14,230
lines is received after the blank line (not shown here).
The last line is the output by the client.

27.48
Example 27.3 (continued)

27.49
Note

HTTP version 1.1 specifies a persistent


connection by default.

27.50
Computer Science & Engineering
Assignment

Semester- VI (I & II) Branch: CSE

Subject with Code: Computer Networks (IT-305-F)

Q:1 Explain the Following.


1. SMTP,
2. POP,
3. IMAP;
4. FTP,
5. HTTP

26.51

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy