Re: [Lurker-users] Permissions errors

On Mon, Sep 21, 2009 at 12:47 AM, Gerald Livingston <
gerald.lurker@sysmatrix.net> wrote:

> > A better test would be to make your sell script:
> > "touch /tmp/test-file". Then run it and see who
> > created/owns /tmp/test-file.
>
> nobody:nogroup
>

Well that would explain why you can't write to the lurker database.

LDA's like procmail require a local user so they can get around the
> chroot.


I'm not sure what you mean here. chroot has nothing to do with user
accounts; it just changes the root directory.


> I'm using ecartis as a mailing list manager and it "just works"
> with nothing but aliases.
> list1: "|/usr/lib/ecartis/ecartis -s list1"
>

Interesting. Perhaps it's setuid? Or perhaps there is a setting somewhere
else that instructs the MDA to setuid for it.
On Mon, Sep 21, 2009 at 12:47 AM, Gerald Livingston &lt;gerald.lurker@sysmatrix.net&gt; wrote:
&gt; A better test would be to make your sell script:
&gt; &quot;touch /tmp/test-file&quot;. Then run it and see who
&gt; created/owns /tmp/test-file.

nobody:nogroupWell that would explain why you can&#39;t write to the lurker database.

LDA&#39;s like procmail require a local user so they can get around the
chroot.I&#39;m not sure what you mean here. chroot has nothing to do with user accounts; it just changes the root directory. 
I&#39;m using ecartis as a mailing list manager and it &quot;just works&quot;
with nothing but aliases.
list1: &quot;|/usr/lib/ecartis/ecartis -s list1&quot;Interesting. Perhaps it&#39;s setuid? Or perhaps there is a setting somewhere else that instructs the MDA to setuid for it.