Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!mips!twg.com!david From: david@twg.com (David S. Herron) Newsgroups: comp.unix.sysv386 Subject: Re: SMTP port not listened Keywords: SMTP MMDF TCP/IP Message-ID: <8183@gollum.twg.com> Date: 30 Oct 90 01:42:41 GMT References: <471@sdipl.oz> Reply-To: david@twg.com (David S. Herron) Organization: The Wollongong Group, Palo Alto, CA Lines: 44 In article <471@sdipl.oz> petem@sdipl.oz (Peter Mason) writes: >Which process in the SCO system is supposed to be monitoring this port, >and how do we get it started up? smtpsrvr handles the SMTP protocol and can be started directly from inetd, if you like smtpd (if it's there) comes in two slightly different flavors. One does inetd-like things (waits on a connection and starts smtpsrvr with the incoming socket/connection attached to std{in,out}). The other is meant to be run from inetd. From one of our SCO systems here, a line from /etc/inetd.conf: smtp stream tcp nowait mmdf /usr/mmdf/chans/smtpd smtpd /usr/mmdf/chans/smtpsrvr smtp The fields are as follows: "smtp" name of service "stream tcp" type of socket to do "nowait" don't wait for the daemon to finish before continuing to listen to connections (?) "mmdf" user ID to run the command as "/usr/mmdf/..." the command /usr/mmdf/chans/smtpd is the program to run, and 'smtpd' is argv[0]. The arguments are: program to run when a connection starts, and the channel through which the mail is to enter the system. This is on an SCO/ODT system -- I dunno what it looks like on an SCO/Unix system but assume it's more-or-less identical. The arguments to smtpsrvr are (in case you feel like bypassing inetd) smtpsrvr them us channel[,channel,channel,...] "them" and "us" are the names of the remote and local ends of the connection, respectively. -- <- David Herron, an MMDF & WIN/MHS guy, <- Formerly: David Herron -- NonResident E-Mail Hack <- <- Use the force Wes!