Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!usc!apple!agate!violet.berkeley.edu!cliff
From: cliff@violet.berkeley.edu (Cliff Frost)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: New Host-Requirement RFCs
Message-ID: <1989Oct27.212939.11277@agate.berkeley.edu>
Date: 27 Oct 89 21:29:39 GMT
References: <8910252236.AA14405@alw.nih.gov> <KARL.89Oct27124632@cheops.cis.ohio-state.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Organization: University of California, Berkeley
Lines: 15

In article <KARL.89Oct27124632@cheops.cis.ohio-state.edu> karl@cheops.cis.ohio-state.edu (Karl Kleinpaste) writes:
>...
>If it isn't trivial to do, then the organization's internal mailer
>arrangement is in a serious state of disrepair, and deserves to be
>overhauled anyway.

That's accurate enough (modulo the negative tone).  In other words: "If the
problem faced by a mail-relay is trivial, then it is trivial to solve."

The fact remains that universal MX records don't relieve all mail-relays
of the need to do source routing.  I'm sure the Host Requirements folks
understood the problem, but whichever way they could go is imperfect so
looks like they stayed with Architectural Purity.

	Cliff Frost