Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!bbn!bbn.com!rsalz
From: rsalz@bbn.com (Rich Salz)
Newsgroups: comp.mail.uucp
Subject: Re: registering UUCP sites
Message-ID: <1218@fig.bbn.com>
Date: 18 Nov 88 16:11:14 GMT
References: <1165@fig.bbn.com> <124@minya.UUCP>
Organization: BBN Systems and Technologies Corporation
Lines: 38

Me:
> Just don't complain when domain-only sites start turning up
> and they refuse to send mail to you.

jc@minya.UUCP (John Chambers):
>Time once again to point out that uucp is not an email package;
>it is a file-transfer package, with email layered on top of it.
>
>This isn't a facetious bit of pickiness.  It is quite common to
>make transient uucp hookups (often via a null-modem cable) for
>the purpose of transferring a few Mbytes of files into a machine,
>and then unplug them and carry one of them off somewhere.  If
>doing this required registering with some bureaucracy somewhere,
>it would change a few-minutes job to a few-weeks job.
Fine.  Just don't complain when a domain-only site refuses to send
mail to you.  This is not a facetious repetition.  I said "a" won't
work, you said "but I wanna do b."  Read carefully.

NOBODY requires that the UUCP name match the domain name.  It's a
lot easier, but it is NOT required.

Finally, there is no bureacracy somewhere that requires you to
fill do ANY paperwork.  When you unpack your new machine you call
somebody INSIDE YOUR ORGANIZATION and say "anybody using the
name 'host'?"

>  Why should their internal use of uucp for file transfer
>obligate them to fill out papers for some outside email authority 
>that they've often never even heard of?

It doesn't require any outside authority:
	No mail?  No domain name necessary.
	Domain name necessary?  Ask your local authority.

Got it?
	/rich $alz
-- 
Please send comp.sources.unix-related mail to rsalz@uunet.uu.net.