Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!orion.oac.uci.edu!ucivax!jromine From: jromine@buckaroo.ics.uci.edu (John Romine) Newsgroups: comp.mail.mh Subject: Re: Problems with whatnow/send Message-ID: <279E296F.1830@ics.uci.edu> Date: 24 Jan 91 00:25:19 GMT References: <1991Jan23.230046.7267@mp.cs.niu.edu> Reply-To: jromine@ics.uci.edu (John Romine) Distribution: comp Organization: UC Irvine Department of ICS Lines: 29 Nntp-Posting-Host: buckaroo.ics.uci.edu rickert@mp.cs.niu.edu (Neil Rickert) writes: > What exactly are the benefits of using SMTP with mh? Well, the primary one I know of is that you don't have to run a Mail Transport Agent on every host. When you have several hundred client workstations, it's a major hassle to manage a Sendmail (or MMDF, etc.) on every one of them. The mh-mts(8) man page (part of the MH Administrators Guide) talks about this. If you're managing a single large host, instead of a network of workstations, you probably don't need the "/smtp" option. If you do use the "/smtp" option, you should supply a good list of SMTP hosts in your mtstailor file. One method would be to have every client's NFS server run an MTA, and include that at the front of the client's "servers" list. This assumes that if the NFS server is down, so is the client; this way you probably only have to run 1/10 as many MTAs. At UCI, we have three machines out of 200+ which run an MTA. If all three of them are down, chances are everything else is too. > Without SMTP ... sendmail will ... look up your full name in the > password file if you didn't define a signature. There are plenty of ways to fix this, the easiest would be to ask Bug-MH@ics.uci.edu to change it. The next easiest is to just change mts.c yourself to do what you want, and send your changes to Bug-MH. -- John Romine