Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: mit-amt!sokolov%media-lab.media.mit.edu@eddie.mit.edu (Michael Sokolov)
Newsgroups: comp.sys.sun
Subject: Re: Can someone please help me with setting up mail
Message-ID: <3413@mit-amt>
Date: 3 Jan 89 13:59:56 GMT
References: <178@h.cs.wvu.wvnet.edu>
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 18
Approved: Sun-Spots@rice.edu
Original-Date: 21 Dec 88 15:59:18 GMT
X-Sun-Spots-Digest: Volume 7, Issue 84, message 5 of 14

fuhrman@b.coe.wvu.wvnet.edu (Cris Fuhrman) writes:
>How do I set up the mail so that any user can get any mail from any sun?
>...

I have exactly the same set-up on my lab's suns; shared /usr/spool/mail
directory; actually /usr/spool/mail is in /private (in the / partition) on
our machines, so I've had to specifically mount the server's
/private/usr/spool/mail on each node's /usr/spool/mail directory.

But in any case, I had the same problem with "nobody" ending up owning the
spool files. This is caused by the mailer on one of the client machines
attempting to write into the host's spool directory: the mailer (which
runs as nobody) doesn't have permission to "chown" the spool files on
another machine. My solution has been to require that all mail be
delivered to the server. Everybody has a .forward file which allows for
this. It sounds like you might have tried to do this via /usr/lib/aliases;
I'm not sure why that didn't work, but your problem is definitely caused
by the clients doing the delivery...