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!

Read offline with no ads or diagram watermarks!
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 System Overview and Concepts

Previous Topic/Section
TCP/IP Electronic Mail Communication Overview: Message Composition, Submission, Delivery, Receipt, Processing and Access
Previous Page
Pages in Current Topic/Section
1
23
Next Page
TCP/IP Electronic Mail Addresses and Addressing
Next Topic/Section

TCP/IP Electronic Mail Message Communication Model and Device and Protocol Roles
(Page 1 of 3)

The purpose of the electronic mail system as a whole is to accomplish the transmission of electronic mail messages from a user of a TCP/IP internetwork to one or more recipients. In order to accomplish this, a special method of communication is required that makes the electronic mail system quite different from that used by most other protocols. To understand what I mean by this, you need only recognize the difference in communication between sending a letter and making a phone call.

Most TCP/IP protocols are analogous to making a phone call in this respect: the sender and the receiver must both be on the network at the same time. You can't call someone and talk to them if they aren't around to answer the phone. (Yeah, yeah, answering machines and voice mail. Stop interrupting, will you? J) Most TCP/IP protocols are like this: to send a file using FTP, for example, you must make a direct connection from the sender's machine to the recipient's machine. If the recipient's machine is not on the network at the exact time that sender's is, no communication is possible.

For electronic mail, this type of communication is simply unacceptable. Electronic mail is like its real-world counterpart; Joe wants to be able to put a message into the system at a time that is convenient for him, and Ellen wants to be able to receive Joe's mail at a time that works for her. For this to work, e-mail must use a “send and forget” model, just like real mail, where Joe drops the “envelope” into the e-mail system and it eventually gets to its destination.

This decoupling of the sender and receiver is critical to the design of the electronic mail system. This is especially true because many of the users of Internet electronic mail are not on the Internet all the time. Just as you wouldn't want real mail to be rejected if it arrived when you are not home, you don't want electronic mail to not be delivered if you are not on the Internet when it arrives. Similarly, you may not want to be connected to the Internet for the entire time it takes to write a message, especially if you have access to the Internet for only a limited amount of time each day.

Also critical to the entire electronic mail system is that idea that communication is between specific users, and not between particular machines. This makes e-mail inherently different than many other types of communication on TCP/IP internetworks. We'll see more of why this is important when we look at e-mail addressing.


Previous Topic/Section
TCP/IP Electronic Mail Communication Overview: Message Composition, Submission, Delivery, Receipt, Processing and Access
Previous Page
Pages in Current Topic/Section
1
23
Next Page
TCP/IP Electronic Mail Addresses and Addressing
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.