Re: -ERR being read already /usr/spool/mail/<username>

["Tim Grossner" <tg@cityscape.net>]

The thing of it is...when you put Qpopper on it, it works fine...without
changing permissions or anything. I have seen almost all the Slack boxes I
have worked on do this...Qpopper fixes it every time.


Tim
tg@cityscape.net
-----Original Message-----
From: Steven Pritchard <steve@silug.org>
To: luci-discuss@luci.org <luci-discuss@luci.org>
Date: Monday, November 02, 1998 2:44 AM
Subject: Re: -ERR being read already /usr/spool/mail/<username>


>
>> What would be causing this nonsense?
>> Its occurring for every account.
>> So, mail is unable to be POPped.
>
>Most likely /{var,usr}/spool/mail is not writable by group mail.
>
>For dot-locking to happen, all mail programs have to run as root or
>setgid mail (much safer), and that directory has to be owned and
>writable by the mail group.
>
>Steve
>--
>steve@silug.org           | Linux Users of Central Illinois
>(217)698-1694             | Meetings the 4th Tuesday of every month
>Steven Pritchard          | http://www.luci.org/ for more info
>
>--
>To unsubscribe, send email to majordomo@luci.org with
>"unsubscribe luci-discuss" in the body.
>


--
To unsubscribe, send email to majordomo@luci.org with
"unsubscribe luci-discuss" in the body.