Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.mail,net.news.adm,net.news.sa
Subject: Re: uucp mail vs. MMDF
Message-ID: <1326@umcp-cs.UUCP>
Date: Sat, 24-Nov-84 01:26:46 EST
Article-I.D.: umcp-cs.1326
Posted: Sat Nov 24 01:26:46 1984
Date-Received: Sun, 25-Nov-84 08:45:22 EST
References: <1870@nsc.UUCP> <1871@nsc.UUCP> <117@msdc.UUCP>
Distribution: net
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 20

I don't think that's the real problem: it's not that MMDF saw the @ and
said, "aha, ARPA host", it's that it couldn't find a route to
nsc.UUCP.  The check is done by a substitute /bin/rmail, and it has a
permission check that says something like this:

	if source host is in "senders.ok" then OK
	else if destination host is in "uucp.hosts" then OK
	else error

It does NOT actually check for ARPA hosts!  Back when we were running
MMDF 1 under 4.1, if someone sent mail through us to ``foovax!bar'',
where we'd never heard of foovax, they'd get that nasty-looking note.

I don't think MMDF II has anything better....
-- 
(This line accidently left nonblank.)

In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (301) 454-7690
UUCP:	{seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland