Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!TRANSARC.COM!Craig_Everhart
From: Craig_Everhart@TRANSARC.COM
Newsgroups: comp.soft-sys.andrew
Subject: Re: Bug in mswp.c
Message-ID: <IaxbXwP0BwwO5DOFUf@transarc.com>
Date: 18 Sep 90 19:43:56 GMT
References: <Aaxaoiu0M2YtAFIRw1@thumper.bellcore.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 19

I don't believe that the host name validation code works at all in the
UUCP-connected case, so my inclination would be to turn latype_Remote
into MSWP_GOODNETMAIL if you're trying to run with AMS_UUCPSupported.

Thus, let's replace the section that Nathaniel quoted:

    } else {
	*ErrCode = MSWP_UNKNOWNNETMAIL;
    }

with the almost-as-simple form:

    } else {
	*ErrCode = (AMS_UUCPSupported ? MSWP_GOODNETMAIL : MSWP_UNKNOWNNETMAIL);
    }

Or does anything in the gethostbyname() family work for UUCP-connected hosts?  I don't think it does--instead, the set of UUCP-connected hosts is listed in the delivery system (e.g. sendmail) and in processes it runs, but nowhere where it's quick to validate from an everyday user process.

		Craig