48 lines
1.6 KiB
HTML
48 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>Forcing Mail to be Transferred 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="node250.html">Preventing Mail from Being </A>
|
|
<B>Up:</B> <A HREF="node246.html">Administrivia and Stupid Mail </A>
|
|
<B> Previous:</B> <A HREF="node248.html">Forcing Mail into Misconfigured </A>
|
|
<BR> <P>
|
|
<H2><A NAME="SECTION0017630000">Forcing Mail to be Transferred via UUCP</A></H2>
|
|
<P>
|
|
<A NAME="8305"></A>
|
|
<A NAME="8465"></A>
|
|
<A NAME="8466"></A>
|
|
<A NAME="8467"></A>
|
|
<A NAME="8468"></A>
|
|
<A NAME="8469"></A>
|
|
<P>
|
|
In an ideal world (from the Internet perspective), all hosts have records in
|
|
the Domain Name Service (DNS) and will send mail with fully qualified domain
|
|
names.
|
|
<P>
|
|
If you happen to talk via UUCP to such a site, you can force mail to go
|
|
through the point-to-point UUCP connection rather than through your default
|
|
mailer by essentially ``undomainizing'' their hostname through the
|
|
uucpxtable.
|
|
<P>
|
|
To force UUCP delivery to sesame.com, you would put the following in
|
|
your uucpxtable:
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
The result is that sendmail will then determine (via
|
|
UUCPNODES in the sendmail.m4 file) that you are
|
|
directly connected to the remote system and will queue the mail for
|
|
delivery with UUCP.
|
|
<P>
|
|
<BR> <HR>
|
|
<P><ADDRESS>
|
|
<I>Andrew Anderson <BR>
|
|
Thu Mar 7 23:22:06 EST 1996</I>
|
|
</ADDRESS>
|
|
</BODY>
|
|
</HTML>
|