Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!osu-eddie!karl
From: karl@osu-eddie.UUCP
Newsgroups: comp.emacs
Subject: Re: Another rmail problem in GNU emacs
Message-ID: <3140@osu-eddie.UUCP>
Date: Mon, 16-Feb-87 21:34:23 EST
Article-I.D.: osu-eddi.3140
Posted: Mon Feb 16 21:34:23 1987
Date-Received: Tue, 17-Feb-87 23:26:22 EST
References: <2939@pegasus.UUCP>
Organization: OSU
Lines: 28
In-reply-to: avi@pegasus.UUCP's message of 16 Feb 87 22:52:31 GMT
Posting-Front-End: GNU Emacs 18.35.1 of Wed Jan 14 1987

avi@pegasus.UUCP writes of problems getting GNU Emacs' rmail to find
mail in /usr/mail/$LOGNAME.

The best solution to this problem is to make $EMACS/etc/movemail
setgid-mail.  All movemail wants to do is pick up your mail file, and
move it wholly elsewhere.  It has to create locking files in order to
obey /bin/mail's synchronization mechanism to avoid simultaneous
updates.  Anything which needs to create those locks must run
setgid-mail.  I do this on my machines, and it works fine.  I
read/write mail/news in GNU Emacs all the time; I haven't typed
"mailx" at a shell prompt in a couple of months.

The reason rmail says you have no new mail is that it ignores the
diagnostic that movemail printed to stderr.  The diagnostic correctly
identifies the problem as an inability to create the lock.  Try
running movemail from a shell prompt; you'll see what I mean.

   >When I got my tar version from Karl, I couldn't even
   >take it apart unless I was suid root.

Apologies.  I created the distribution that I sent to a number of
folks inside AT&T from my working area, which I have write-protected
not for fascist reasons, but rather for simple paranoia against
accidental destruction.  The tar file I sent to several folks caused
troubles when unpacked at the destination, and tar chown'd everything
to uid 239.
-- 
Karl