Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cwjcc!hal!ncoast!allbery
From: allbery@ncoast.ORG (Brandon S. Allbery)
Newsgroups: news.sysadmin
Subject: Re: Stuck with .UUCP forever?
Message-ID: <13756@ncoast.ORG>
Date: 15 Jun 89 23:54:02 GMT
References: <May.22.01.46.36.1989.17215@porthos.rutgers.edu> <444@logicon.arpa> <9415@b-tech.ann-arbor.mi.us> <57064@uunet.UU.NET> <9426@b-tech.ann-arbor.mi.us> <300@capmkt.COM> <9436@b-tech.ann-arbor.mi.us>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery)
Followup-To: news.sysadmin
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 23

As quoted from <9436@b-tech.ann-arbor.mi.us> by zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff):
+---------------
| Why is a uucp site unable to do mail forwarding?  Most do.
+---------------

In this context, "forwarding" means forwarding messages sent via SMTP over a
network from a site with an IP address to a site with an IP address; UUCP is
not and can not be integrated into such a network, it can only be layered on
top of such a network.  That is, a random direct-connected Internet site can
not send mail to NCoast.ORG by having the nameserver return an [xx.yy.zz.ww]
IP address pointing to ncoast from an "A" record in the nameserver.  We have
to have a forwarder; that is, we have an "MX" record in the nameserver which
gives the IP address (indirectly, via another lookup?  I dunno, but it
doesn't really matter) of our forwarder; and our forwarder must be capable
of recognizing that even though the message was sent to them, it's really
for us.

++Brandon
-- 
Brandon S. Allbery, moderator of comp.sources.misc	     allbery@ncoast.org
uunet!hal.cwru.edu!ncoast!allbery		    ncoast!allbery@hal.cwru.edu
      Send comp.sources.misc submissions to comp-sources-misc@<backbone>
NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser