old-www/LDP/nag/node236.html

53 lines
1.9 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>uucpxtable</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="node237.html">pathtable</A>
<B>Up:</B> <A HREF="node234.html">A Tour of Sendmail+IDA </A>
<B> Previous:</B> <A HREF="node235.html">mailertable</A>
<BR> <P>
<H2><A NAME="SECTION0017420000">uucpxtable</A></H2>
<P>
<A NAME="8423"></A>
<A NAME="8424"></A>
<A NAME="8425"></A>
<A NAME="8426"></A>
<A NAME="8427"></A>
<P>
Usually, mail to hosts with fully-qualified domain names is delivered via
Internet style (SMTP) delivery using Domain Name Service (DNS), or via the
relay host. The uucpxtable forces delivery via UUCP routing by
converting the domainized name into a UUCP-style un-domainized remote
hostname.
<P>
It is frequently used when you're a mail forwarder for a site or domain or
when you wish to send mail via a direct and reliable UUCP link rather than
potentially multiple hops through the default mailer and any intermediate
systems and networks.
<P>
UUCP sites that talk to UUCP neighbors who use domainized mail headers would
use this file to force delivery of the mail through the direct UUCP
point-to-point link between the two systems rather than using the less direct
route through the RELAY_MAILER and RELAY_HOST or
through the DEFAULT_MAILER.
<P>
Internet sites who do not talk UUCP probably would not use the
uucpxtable.
<P>
Suppose you provide mail forwarding service to a system called
sesame.com in DNS and sesame in the UUCP maps. You would need
the following uucpxtable entry to force mail for their host to go
through your direct UUCP connection.
<P>
<P><P><BR> <HR>
<P><ADDRESS>
<I>Andrew Anderson <BR>
Thu Mar 7 23:22:06 EST 1996</I>
</ADDRESS>
</BODY>
</HTML>