Bug in "/usr/lib/sendmail" in Sun UNIX release 2.0.
Brian Kantor
brian at sdcsvax.UUCP
Sun Oct 20 21:11:27 AEST 1985
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 at ucsd.arpa
akgua >--- sdcsvax --- brian
ucbvax/ Kantor at Nosc
More information about the Comp.unix
mailing list