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!

The whole site in one document for easy reference!
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 Addresses and Addressing

Previous Topic/Section
TCP/IP Electronic Mail Addresses and Addressing
Previous Page
Pages in Current Topic/Section
12
3
Next Page
TCP/IP Historical and Special Electronic Mail Addressing
Next Topic/Section

TCP/IP Electronic Mail Addressing and Address Resolution
(Page 3 of 3)

The Special Requirements of E-Mail Addresses

Having e-mail addressing refer to the user's local SMTP server provides a great deal of flexibility compared to having addresses mention a specific client computer. But it doesn't provide enough flexibility to handle various situations:

  • An organization may want to use “generic” addresses that do not specify the name of the SMTP server to handle mail. The reason is that this requires people sending them mail to know the name of that server. For example, if someone knew my real name and that I was at MIT, it would be easier for them to remember my old e-mail address as “cmk@mit.edu” than “cmk@athena.mit.edu”.

  • An administrator may change which machines handle mail over a period of time. This would mean all the users's e-mail addresses would have to change— and most of us know what a pain that is. For example, if I moved from the “athena” machine to the “jabberwocky” machine, my old address would have needed to change to “cmk@jabberwocky.mit.edu”. But if it were just “cmk@mit.edu” the change would not affect me.

  • In larger organizations, it might be desirable to have multiple servers share the load of handling incoming mail.
The Mail Exchange (MX) DNS Record

To address all of these requirements, the DNS system includes a feature that was specifically designed to support electronic mail addressing. A special mail exchange (MX) record can be set up that specifies which SMTP server should be used for mail coming in to a particular domain name. If properly configured, this allows considerable flexibility to handle the cases I described above and more. For more details, please see the description of the MX record and DNS electronic mail support.

For example, I am the owner of the “pcguide.com” domain name. E-mail can be sent to me at “pcguide.com”, but it is not actually stored on any server by that name. It is redirected to the real server where my inbox is located. This allows me to handle all incoming mail to “pcguide.com” regardless of where my mailbox is actually located.

DNS is also significant in that its “MX” resource records eliminated the need to “relay” e-mail from one SMTP server to the next to deliver it. In modern TCP/IP it is possible to send e-mail directly from the sender's SMTP server to the recipient's, making communication faster and more efficient. See the section devoted to SMTP for details.

Key Concept: Some form of addressing is required for all network communication; since electronic mail is user-oriented, e-mail addresses are based on users as well. In modern TCP/IP e-mail, standard addresses consist of a user name, which specifies who the recipient is, and a domain name, which specifies the DNS domain where the user is located. A special DNS mail exchange (MX) record is set up for each domain that accepts e-mail, so a sending SMTP server can determine what SMTP server it should use to send mail to a particular recipient.



Previous Topic/Section
TCP/IP Electronic Mail Addresses and Addressing
Previous Page
Pages in Current Topic/Section
12
3
Next Page
TCP/IP Historical and Special Electronic Mail 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.