🚀 go-pugleaf

In <BsKGyo.9G3@world.std.com> sandyb@world.std.com (Sandy Bendremer) writes:
>1.  Our systems still starts up with smtpd running in the background.  In
>this state, 'sendmail -bd' will not create a background process (it just
>exits).  If smtpd is killed, sendmail will run in the background!  What is
>the proper configuration??

If you run sendmail in daemon mode the smtpd must not be started. You
can't have both programs listening on the SMTP port for incoming mail.

>2.  Do we only need to worry about sendmail's configuration, or do some of
>the other AT&T configuration files still have an effect??

/bin/mail and mailx both access the AT&T configurations files and
interpret the instructions in them. Because of that alone, I consider the
SVR4 mail system a complete botch. Also note that the AT&T mail system
and the sendmail don't work together very well.

>4.  AT&T's mailx only works on local addresses?  Should we just forget 
>about this now that we're using sendmail?  Elm our primary agent is OK.

Forget it or install the 4.3-reno or NET-2 Mail to get a similar user
interface.

>5.  Any general hints/comments on using sendmail on SVR4 are appreciated.

How about some bugs?

- frozen configuration files don't work. You get a core dump.
- sendmail is unable to deliver local mail with the AT&T /bin/mail.
- /usr/ucblib/binmail gets the permissions wrong on the local mailboxes.
- sendmail's mailq really should be /var/spool/mqueue.


-- 
				Christoph Badura  ---  bad@flatlin.ka.sub.org

ISO? Nicht immer, aber immer M-vfter.