Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!MRFLOODS.CC.UMICH.EDU!paul
From: paul@MRFLOODS.CC.UMICH.EDU ('da Kingfish)
Newsgroups: comp.sys.apollo
Subject: Re: question regarding sendmail
Message-ID: <8804071710.AA00247@mrfloods.cc.umich.edu>
Date: 7 Apr 88 17:10:15 GMT
References: <1740@devvax.JPL.NASA.GOV>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 30


 
 
Are you running sendmail -bd on the Apollos?  Look in your sun's
/etc/rc.* files, and see how sendmail starts.  Probably something like
"/usr/lib/sendmail -bd -q1h" or something.  Sendmail listens on the smtp
port, and if it's not, you'll see the connection refused message.

Make sure /bin/mail is run as root, or can create files in a
/usr/spool/mail directory, which should also exist.   Make sure
sendmail can exec a /bin/mail, as well.  We run sendmail as root, and
/bin/mail is setuid root, too.

An easy way to see what /bin/mail is getting is to replace
(temporarily, so save a copy) /bin/mail with a shell called /bin/mail
that looks like this:

#!/bin/sh
echo $* > /tmp/binmail.$$ 
cat - >> /tmp/binmail.$$ 
exit 0

Make that mode 555, or whatever, so you know any user could execute
it.

You want to see the args and the message contents, basically.  Flags
for Mlocal in sendmail.cf could be something like "F=rlsDFMmn".
"A=mail -d $u" is needed, too.  If binmail gets invoked as "mail -d
paul@host" instead of "mail -d paul" something else is wrong too.

--paul