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 Addresses and Addressing

Previous Topic/Section
TCP/IP Electronic Mail Addressing and Address Resolution
Previous Page
Pages in Current Topic/Section
1
2
Next Page
TCP/IP Electronic Mail Aliases / Address Books, Multiple Recipient Addressing and Electronic Mailing Lists
Next Topic/Section

TCP/IP Historical and Special Electronic Mail Addressing
(Page 2 of 2)

UUCP-Style Addressing

An older address style commonly associated with e-mail was the “UUCP style” address. The Unix-to-Unix Copy Protocol (UUCP) was commonly used years ago to route mail before SMTP became widely deployed (again, it is still used, just not as much as before). The addresses in this system are specified as a path of hosts separated by exclamation marks (“!”). The path dictates the route that mail takes to get to a particular user, passing through a series of intermediate machines running UUCP. For example, if mail to “joe” at the host “joesplace” had to go through three hosts “host1”, “host2” and “host3”, the address would be:

host1!host2!host3!joesplace!joe

Since the slang term for an exclamation mark is “bang”, this came to be called bang path notation.

The use of UUCP style notation was sometimes mixed with TCP/IP style domain name address notation when DNS came into use. So you might have seen something like “host1!user@domain”. There was some confusion in how exactly to interpret such an address: does it mean to send mail first to “host1” and then to “user@domain”? Or does it mean to first send it to the “domain” which then goes to “user” at “host1”? There was no universal answer to this. The problem was mostly resolved both by the decrease in use of UUCP and the move on the part of UUCP systems to TCP/IP style domain name addressing.

Addressing for Gatewaying

Finally, you may encounter e-mail addresses that appear like multiple TCP/IP addresses that have been nested using unusual punctuation. For example, you may see something that looks like this:

user%domain1.com@subdomain.domain2.edu

This is a way of addressing sometimes seen when e-mail gateways are used; it will cause the mail to be sent to “user%domain1.com” at “subdomain.domain2.edu”. The address then is interpreted as “user@domain1.com”. However, again, not all systems are guaranteed to interpret this the same way.

E-mail gatewaying is not a simple matter in general, and as you can see, one reason is the use of different e-mail address styles and the problems of consistency in how complex “hybrid” addresses are interpreted, as discussed above. However, as the Internet expands and TCP/IP becomes more widespread, it is becoming less and less common to see these older, special address formats in use. They are becoming more and more a “historical curiosity” (unless you happen to use one of them!)


Previous Topic/Section
TCP/IP Electronic Mail Addressing and Address Resolution
Previous Page
Pages in Current Topic/Section
1
2
Next Page
TCP/IP Electronic Mail Aliases / Address Books, Multiple Recipient Addressing and Electronic Mailing Lists
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.