40 lines
1.6 KiB
HTML
40 lines
1.6 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
|
|
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE>How does Mail Routing Work?</TITLE>
|
|
</HEAD>
|
|
<BODY LANG="EN">
|
|
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
|
|
<B> Next:</B> <A HREF="node191.html">Mail Routing on the </A>
|
|
<B>Up:</B> <A HREF="node186.html">Electronic Mail</A>
|
|
<B> Previous:</B> <A HREF="node189.html">Email Addresses</A>
|
|
<BR> <P>
|
|
<H1><A NAME="SECTION0015400000">How does Mail Routing Work?</A></H1>
|
|
<A NAME="mailrouting"></A>
|
|
The process of directing a message to the recipient's host is called
|
|
<em>routing</em>. Apart from finding a path from the sending site to the
|
|
destination, it involves error checking as well as speed and cost
|
|
optimization.
|
|
<P>
|
|
There is a big difference between the way a UUCP site handles routing,
|
|
and the way an Internet site does. On the Internet, the main job of
|
|
directing data to the recipient host (once it is known by it's
|
|
IP-address) is done by the IP networking layer, while in the UUCP zone,
|
|
the route has to be supplied by the user, or generated by the mail
|
|
transfer agent.
|
|
<P>
|
|
<BR> <HR>
|
|
<UL>
|
|
<LI> <A HREF="node191.html#SECTION0015410000">Mail Routing on the Internet</A>
|
|
<LI> <A HREF="node192.html#SECTION0015420000">Mail Routing in the UUCP World</A>
|
|
<LI> <A HREF="node193.html#SECTION0015430000">Mixing UUCP and RFC-822</A>
|
|
</UL>
|
|
<BR> <HR>
|
|
<P><ADDRESS>
|
|
<I>Andrew Anderson <BR>
|
|
Thu Mar 7 23:22:06 EST 1996</I>
|
|
</ADDRESS>
|
|
</BODY>
|
|
</HTML>
|