Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site sdcsvax.UUCP Path: utzoo!linus!decvax!ittatc!dcdwest!sdcsvax!brian From: brian@sdcsvax.UUCP (Brian Kantor) Newsgroups: net.bugs.4bsd,net.unix Subject: Re: Bug in "/usr/lib/sendmail" in Sun UNIX release 2.0. Message-ID: <1150@sdcsvax.UUCP> Date: Sun, 20-Oct-85 07:11:27 EDT Article-I.D.: sdcsvax.1150 Posted: Sun Oct 20 07:11:27 1985 Date-Received: Mon, 21-Oct-85 06:51:43 EDT References: <669@dcl-cs.UUCP> <674@dcl-cs.UUCP> <200@l5.uucp> Reply-To: brian@sdcsvax.UUCP (Brian Kantor) Organization: UCSD wombat breeding society Lines: 30 Xref: linus net.bugs.4bsd:1514 net.unix:5371 Summary: We too had the Sun 2.0 frozen configuration sendmail problem, evinced by a receiving sun instantly closing the TCP connection. Because most of our Sun workstations are short on memory (1 meg) and therefore slow, I wanted to use the frozen configuration file. It turns out that, in our cluster of suns anyway, the sendmail that was on the Sun 1.[0-4] system seems to work just fine with the frozen configuration file. How to tell if a sun you're having problems with is running the new or the old sun sendmail version: 1. Kill the /usr/lib/sendmail.fc file on the questioned machine. 2. From another sendmail-equipped system, send it mail with the -v (verbose) flag on, and watch the conversation. If the DATA message is greeted with 354 Lay it on me, baby! you have the newer version of sendmail running on the destination sun. Older versions said something much more boring. Something to keep in mind: sendmail stores the host name in the frozen configuration. If you have the .fc file in a NFS shared file system, and freeze it (sendmail -bz) on the server, all the clients will report their hostname in mail as being the server. You may actually want this to happen, although I don't think that's really the right way to do it. Brian Kantor UC San Diego decvax\ brian@ucsd.arpa akgua >--- sdcsvax --- brian ucbvax/ Kantor@Nosc