<!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>Relay Systems and Mailers</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="node231.html">The Various Configuration Tables</A> <B>Up:</B> <A HREF="node223.html">Typically Used sendmail.m4 Parameters</A> <B> Previous:</B> <A HREF="node229.html">UUCP-Related Items</A> <BR> <P> <H3><A NAME="SECTION0017327000">Relay Systems and Mailers</A></H3> <P> <A NAME="8410"></A> <A NAME="8411"></A> <A NAME="8412"></A> <P> <P><P> <P> Many system administrators do not want to be bothered with the work needed to ensure that their system is able to reach all the networks (and therefore systems) on all networks worldwide. Instead of doing so, they would rather relay all outgoing mail to another system that is known to be indeed ``smart''. <P> RELAY_HOST defines the UUCP hostname of such a smart neighboring system. <P> RELAY_MAILER defines the mailer used to relay the messages there. <P> It is important to note that setting these parameters results in your outgoing mail being forwarded to this remote system, which will affect the load of their system. Be certain to get explicit agreement from the remote Postmaster before you configure your system to use another system as a general purpose relay host. <P> <BR> <HR> <P><ADDRESS> <I>Andrew Anderson <BR> Thu Mar 7 23:22:06 EST 1996</I> </ADDRESS> </BODY> </HTML>