Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

Searchable, convenient, complete TCP/IP information.
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  TCP/IP Key Applications and Application Protocols
           9  TCP/IP File and Message Transfer Applications and Protocols (FTP, TFTP, Electronic Mail, USENET, HTTP/WWW, Gopher)
                9  TCP/IP Electronic Mail System: Concepts and Protocols (RFC 822, MIME, SMTP, POP3, IMAP)
                     9  TCP/IP Electronic Mail Delivery Protocol: The Simple Mail Transfer Protocol (SMTP)

Previous Topic/Section
SMTP Overview, History and Standards
Previous Page
Pages in Current Topic/Section
12
3
Next Page
SMTP Connection and Session Establishment and Termination
Next Topic/Section

SMTP Communication and Message Transport Methods, Client/Server Roles and Terminology
(Page 3 of 3)

SMTP Terminology: Client/Server and Sender/Receiver

The original RFC 821 standard referred to the device that initiates an SMTP e-mail transfer as the sender and the one that responds to it as the receiver. These terms were changed to client and server in RFC 2821 to “reflect current industry terminology”. Strictly speaking, this is correct, but in some ways the more current terminology is significantly less clear.

As I explained in the general discussion of TCP/IP client/server operation, the terms “client” and “server” are used in many different sense in networking, and this often leads to confusion. In common parlance, the computers that handle e-mail on the Internet are usually all called SMTP servers. This is for two reasons. First, they run SMTP server software to provide SMTP services to client machines, such as end-user PCs. Second, these devices are usually dedicated hardware servers running in network centers, typically managed by Internet Service Providers.

However, the terms “client” and “server” are now used to refer to the roles in a particular SMTP communication as well. Since all SMTP servers both send and receive e-mail, they all act as both clients and servers transactionally at different times. An SMTP server that is relaying an e-mail will act as both for that message, receiving it as a server and then sending it to the next server as a client.

Adding to this potential confusion is the fact that the initial stage in sending an e-mail is from the sender's client machine to the sender's local SMTP server. Thus, the client role in an SMTP transaction may not be an actual SMTP server, but the server role will always be a server.

Confused yet? J Me too. For all of these reasons, the old terms “sender” and “receiver” are still used in places in RFC 2821, where needed for clarity. I consider them much more straight-forward and use them in the topics that follow.

Key Concept: SMTP servers both send and receive e-mail; the device sending mail acts as a client for that transaction; the one receiving it acts as a server. To avoid confusion, it is easier to refer to the device sending e-mail as the SMTP sender and the one receiving as the SMTP receiver; these were the terms used when SMTP was originally created.



Previous Topic/Section
SMTP Overview, History and Standards
Previous Page
Pages in Current Topic/Section
12
3
Next Page
SMTP Connection and Session Establishment and Termination
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.