Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!samsung!uunet!jarthur!ucivax!jromine
From: jromine@buckaroo.ics.uci.edu (John Romine)
Newsgroups: comp.mail.mh
Subject: Re: Problems with whatnow/send
Message-ID: <27A47A8D.376@ics.uci.edu>
Date: 28 Jan 91 19:25:01 GMT
References: <5740009@hpscdc.scd.hp.com> <27A451FD.10013@ics.uci.edu> <1991Jan28.182047.16421@mp.cs.niu.edu>
Reply-To: jromine@ics.uci.edu (John Romine)
Organization: UC Irvine Department of ICS
Lines: 14
Nntp-Posting-Host: buckaroo.ics.uci.edu

rickert@mp.cs.niu.edu (Neil Rickert) writes about /bin/mail:
>   1.  [/bin/mail] will deliver mail to a user's mailbox.
>   It is used in this way by [an MTA] to achieve final mail delivery.

Yes, this is why you replace /bin/mail with "mhmail" only on systems
which don't run an MTA.  On systems *with* an MTA, you would simply use
/bin/mail as-is to put the mail in /usr/spool/mail/username.

If your local situation works better by running a sendmail on every
machine and having MH fork/exec a sendmail to post mail, by all means
do that.  MH can support a more flexible posting method (SMTP), but it
is not required.
--
John Romine