Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!iuvax!rutgers!mcnc!wolves!ggw
From: ggw@wolves.uucp (Gregory G. Woodbury)
Newsgroups: comp.mail.uucp
Subject: Re: Who pays the bill?
Message-ID: <1990Aug8.214750.1614@wolves.uucp>
Date: 8 Aug 90 21:47:50 GMT
References: <26A738A8.725B@tct.uucp> <Jul.22.17.30.26.1990.1282@turbo.bio.net> <Jul.30.17.57.18.1990.9079@turbo.bio.net> <65793@sgi.sgi.com> <7704@gollum.twg.com> <1990Aug6.230109.4220@ibmpa>
Organization: Wolves Den UNIX and Usenet node
Lines: 22

In <1990Aug6.230109.4220@ibmpa> steve@qe2.paloalto.ibm.com (Steve DeJarnett) writes:
>
>	Of course, then we get to the following problem.  apple.sgi.com is a
>FQDN.  Great.  Now the Rabid Rerouters pop up, and say "great, a FQDN very near
>the end of the path (actually, at the end).  Let's short-circuit to that."
>BOING!  If apple.sgi.com isn't Internet-connected, and doesn't have anyone
>MX-ing for it, the mail bounces.

	Wrong,  if it isn't directly connected, and does not have a
valid MX record at the appropriate hosts,  IT IS NOT A FQDN!  The DNS is
a fully controlled system,  the fact that some people abuse it and use
domains without insuring MX'ing is in place, that is THEIR error and
problem.
	Personally, I think a machine handling mail has the right to
reroute IF it can GUARANTEE proper delivery.  If there is a valid FQDN
further to the right, call the resolver and find its mailbox that is
directly connected and drop it there for handling.
-- 
Gregory G. Woodbury @ The Wolves Den UNIX, Durham NC
UUCP: ...dukcds!wolves!ggw   ...mcnc!wolves!ggw           [use the maps!]
Domain: ggw@cds.duke.edu     ggw%wolves@mcnc.mcnc.org
[The line eater is a boojum snark! ]           <standard disclaimers apply>