Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!mintaka!spdcc!tauxersvilli!alphalpha!nazgul
From: nazgul@alphalpha.com (Kee Hinckley)
Newsgroups: comp.sys.apollo
Subject: Re: addressees at APOLLo.COM (Apollo's sendmail)
Message-ID: <1990Oct5.075720.5472@alphalpha.com>
Date: 5 Oct 90 07:57:20 GMT
References: <4d34a015e.000f088@caen.engin.umich.edu>
Organization: asi
Lines: 34

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.
>
>E.g.
>
>What if this sequence fails?
>	pw = getpwuid(geteuid());
That probably explains why every so often all mail starts going
out with a sender apparently picked randomly from the password file.

>In addition to rgy quirks, there is the (different from Unix) apollo
>notion of file concurrency control.  Do you have a high tolerance for
>"Unknown error mailer error #1" messages when /bin/mail exits with a
You should be so lucky.  If there's an rgyd error you are likely to
get a failure in /bin/mail too, and that particular failure doesn't
set any error codes.  /bin/mail will do an exit(0) and the mail will
get thrown away.

By all means pick up a /bin/mail replacement somewhere and make sure
it doesn't have that bug.  Apollo has no plans to fix it.

						-kee


-- 
Alphalpha Software, Inc.	|	motif-request@alphalpha.com
nazgul@alphalpha.com		|-----------------------------------
617/646-7703 (voice/fax)	|	Proline BBS: 617/641-3722

I'm not sure which upsets me more; that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.