old-www/LDP/nag/node250.html

50 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>Preventing Mail from Being Delivered via UUCP</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="node251.html">Running the Sendmail Queue </A>
<B>Up:</B> <A HREF="node246.html">Administrivia and Stupid Mail </A>
<B> Previous:</B> <A HREF="node249.html">Forcing Mail to be </A>
<BR> <P>
<H2><A NAME="SECTION0017640000">Preventing Mail from Being Delivered via UUCP</A></H2>
<P>
<A NAME="8319"></A>
<A NAME="8470"></A>
<A NAME="8471"></A>
<A NAME="8472"></A>
<A NAME="8473"></A>
<A NAME="8474"></A>
<P>
The opposite condition also occurs. Frequently, systems may have a number of
direct UUCP connections that are used infrequently or that are not as reliable
and always available as the default mailer or relay host.
<P>
For example, in the Seattle area there are a number of systems that exchange
the various distributions via anonymous UUCP when the distributions
are released. These systems talk UUCP only when necessary, so it is generally
faster and more reliable to send mail through multiple very reliable hops and
common (and always available) relay hosts.
<P>
It is easily possible to prevent UUCP delivery of mail to a host that you are
directly connected to. If the remote system has a fully-qualified domain name,
you can add an entry like this to the domaintable:
<P>
<P><P>
<P>
This will replace any occurrence of the UUCP name with the FQDN, and thus
prevent a match by the UUCPNODES line in the sendmail.m4 file.
The result is generally that mail will go via the RELAY_MAILER
and RELAY_HOST (or DEFAULT_MAILER).
<P>
<BR> <HR>
<P><ADDRESS>
<I>Andrew Anderson <BR>
Thu Mar 7 23:22:06 EST 1996</I>
</ADDRESS>
</BODY>
</HTML>