Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!cwjcc!hal!ncoast!allbery From: allbery@ncoast.UUCP (Brandon S. Allbery) Newsgroups: comp.mail.uucp Subject: Re: this might be getting out of hand... Message-ID: <12246@ncoast.UUCP> Date: 16 Aug 88 22:55:06 GMT References: <3746@palo-alto.DEC.COM> <3400004@eecs.nwu.edu> Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery) Followup-To: comp.mail.uucp Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 22 As quoted from <3400004@eecs.nwu.edu> by gore@eecs.nwu.edu (Jacob Gore): +--------------- | / comp.mail.uucp / allbery@ncoast.UUCP (Brandon S. Allbery) / Aug 12, 1988 / | >Domain-based mailers *cannot* route to unknown sites! | | Huh? How can ANY mailer route to unknown sites? Where does "domain-based" | fit in? +--------------- I was speaking shorthand. What I meant was: as long as a UUCP mailer knows the *next* system in the path, it doesn't have to know the other systems. But domain-based (i.e. Internet non-UUCP) mailers do not use routing, so they must know the actual destination site! Thus, I can send to some site "foobar" that is unknown to ncoast's mailer if *I* know the path, but someone on CWRU20 (if it still exists; it was a CSNet host) can't without hiding the UUCP syntax from the domain-based mailer and sending the mail to a CSNet/UUCP relay site. ++Brandon -- Brandon S. Allbery, uunet!marque!ncoast!allbery DELPHI: ALLBERY For comp.sources.misc send mail to ncoast!sources-misc