Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: addressees at APOLLo.COM (Apollo's sendmail)
Message-ID: <4d37a7d2.1bc5b@pisa.ifs.umich.edu>
Date: 5 Oct 90 15:04:10 GMT
References: <4d34a015e.000f088@caen.engin.umich.edu>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 19

In article <4d34a015e.000f088@caen.engin.umich.edu>, paul@CAEN.ENGIN.UMICH.EDU (Paul Killey) writes:
  
  compiling 5.61 sendmail on apollos is one thing, but getting
  functionality people assume therein is another.

Agreed.  I have mine set up so that outbound mail simply gets relayed to
another, "smarter" machine.  I am the only user of sendmail on my (logical)
network.  Don't ask me about inbound mail, it will disgust you.

At least on large installation of Apollo nodes that I know of just runs
sendmail on a single node, with a daemon that picks outbound messages out of
a big "pre-sendmail" spool directory.  Individual nodes don't run sendmail
at all, they just run a simple program that inserts messages into the spool
directory.  This clearly doesn't scale well.

Too bad Apollo never did a really good mail system.  The Domain architecture
would seem to be ideally suited to some kind of whiz-bang, distributed NCS
based mailer.  But writing and maintaining mailers is a black hole of
programmer time (as Paul is no doubt aware!)