Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!lll-winken!csd4.milw.wisc.edu!leah!rpi!sun.soe.clarkson.edu!ahd
From: ahd@sun.soe!clutx.clarkson.edu (Drew Derbyshire,,,9143397425)
Newsgroups: comp.mail.uucp
Subject: Re: Domain Registration
Message-ID: <3153@sun.soe.clarkson.edu>
Date: 6 Jun 89 00:19:08 GMT
References: <25270@agate.BERKELEY.EDU>
Sender: news@sun.soe.clarkson.edu
Reply-To: ahd@sun.soe!clutx.clarkson.edu
Distribution: usa
Lines: 13

From article <25270@agate.BERKELEY.EDU>, by wisner@mica.Berkeley.EDU (Bill Wisner):
> (Rahul Dhesi)
>>   <jklsjdf><<<Jkldf>>!%%%!x@b#&*()$jsdfkjljsd;fadf&*7987904klj;l;.BITNET
>>
>>should be a valid address.  It isn't, and that's half the problem.
> 
> Pfthhht. If that address is strictly limited to within BITNET, fine. But

I've got ten bucks if Rahul can give me the name of *one* host acting on
the Bitnet side as a gateway that can handle that address (ignoring the
gateway, UUCP, internet, etc.)  Any internal Bitnet address has to have
an 1-8 character host name for starters, and his example does not
clarify the issue.  Nor does this... oh well.