Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!sun-spots-request
From: asnyder@artorg.hmc.psu.edu (alan snyder)
Newsgroups: comp.sys.sun
Subject: Re: Problems with Sun MX sendmail
Keywords: Networks
Message-ID: <8325@brazos.Rice.edu>
Date: 30 May 90 14:35:15 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 28
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n179
X-Sun-Spots-Digest: Volume 9, Issue 189, message 6

In <8128@brazos.Rice.edu> mb@rex.cs.tulane.edu writes:

>I have recently observed some inconsistent behavior of sendmail on Suns
>around our campus.  This is apparently related to interaction with a
>Pyramid system (REX) which serves as the nameserver for most of the Suns
>on campus.  REX does not run Yellow Pages, but is accessed by the Suns
>because they have REX listed in their resolv.conf file.

>Each Sun has the following line in their sendmail.cf file.

>R$*<@$*$%y>$*           $#ether $@$3 $:$1@$2$3$4        user@this-host

>The way I understand this line, it will recognize any host identified in
>the Yellow Pages.  However, on our CS subnet, this line recognizes any
>host listed in the YPs PLUS any host listed in REX's nameserver database
>(i.e, any host actually loaded into the nameserver cache when named starts
>up).  REX is on the CS subnet.

We have a similar situation here: a small local net where we run yellow
pages and a university-wide net running the name service (our name server
is on another campus, at the other end of a T1 link).

It appears that Sun's sendmail.mx does not look at the Yellow Pages map.
I use the plain sendmail.  Anything found in the yp map is mailed as
above.  Anything  in top-level domains known not to require a mail
exchanger is mailed the same way; the name server takes care of the
address properly.  Any local uucp connections are handled similarly.
Anything else is kicked up to a mail handling machine.