Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!uunet!mcsun!ukc!mucs!cns!umaida!jf
From: jf@ap.co.umist.ac.uk (John Forrest)
Newsgroups: comp.sys.apollo
Subject: Re: senmail / MX records
Message-ID: <1991Mar1.104159@ap.co.umist.ac.uk>
Date: 1 Mar 91 10:41:59 GMT
References: <1991Feb28.173708.39510@eagle.wesleyan.edu> <17411@milton.u.washington.edu>
Sender: news@cns.umist.ac.uk (Usenet news)
Reply-To: jf@ap.co.umist.ac.uk (John Forrest)
Organization: UMIST Computation dept, Manchester, UK
Lines: 35

In article <17411@milton.u.washington.edu>, etb@milton.u.washington.edu (Eric Bushnell) writes:
|> In article <1991Feb28.173708.39510@eagle.wesleyan.edu> hdtodd@eagle.wesleyan.edu writes:
|> >
|> >	Is there a sendmail for the Apollo systems (I run 3500/2500, SR10.2)
|> >that supports MX records?  Has anyone ported newer versions of the code?  Is it
|> >available at an FTP site?
|> >
|> I compiled sendmail 5.65 obtained from an ftp site at U of Illinois.
|> It's working fine at 10.2 and 10.3. You need to undefine the SETPROCTITLE
|> and compile the getloadavg.c that's supplied as a supplementary file.
|> It's available at many sites. I think I got it from uxc.cso.uiuc.edu, 
|> or something like that.

With the latest version from UIUC (5.65a) you don't need to change getloadavg -
it uses the xload one. However, there would appear to be a slight bug on
10.2/3 which is currently being worked on. I'd still mount this version
though, I expect the fix will be a small patch (they usually are) and
generally it seems to work fine.

|> 
|> Now, has anybody got a version of sendmail that works with BIND on a 
|> 10.1 node? Or a version of BIND that works with sendmail?

We run this version (5.65a) on 10.1 - we did the previous IDA version too,
although with more problems. We have "upgraded" BIND to get it to work though
- we ported BIND 4.6 by turning the resolver into an inlib library, adding it
to the system configuration and removing the old resolver entries from the C
library. We've still got the code somewhere if someone is interested - it took
some rewriting of the source, and we never did get the debug stuff to work
properly. However, the resolver works fine, and named did too once you realise
that this also suffers from the SETPROCTITLE problem!

John Forrest
Dept of Computation
UMIST