Re: [Lurker-users] Permissions errors

[Gerald L. <ger...@sy...>]

On Fri, 18 Sep 2009 20:42:03 +0200
legolas558 <leg...@em...> wrote:

> Gerald Livingston ha scritto:
> > I am having GREAT difficulty getting lurker to automagically add new
> > messages to the archive on my Debian system.
> > 
> > Every time I send a message to the archive address I get this in my
> > mail logs:
> > 
> > input/output error. Command output: /var/lib/lurker/db: Permission
> > denied
> > 
> > 
> > Just a permission error, right? But, here are the methods I've
> > tried to use:
> > 
> > 
> > 1. alias bska-archive: "| /usr/bin/lurker-index -l buskatiers -m"
> > 
> > 2. .forward with "| /usr/bin/lurker-index -l buskatiers -m"
> > 
> > They both fail. bska-archive *IS* a real user on the system that is
> > a member of the lurker group. If I 'su - bska-archive' then run
> > lurker-index manually on a mbox file it imports the message just
> > fine so bska-archive *DOES* have correct permissions.
> > 
> > /var/lib/lurker drwxrwsr-x 2 root    lurker  4096 2009-09-18 11:18
> > 
> > from /etc/group:
> > lurker:x:106:mail,postfix,www-data,ecartis,bska-archive
> > 
> > I'm not using procmail or maildrop on this system.
> > 
> Hi Gerald,
> 
> question here is: *WHO* is sending data through a pipe to
> lurker-index? Can you check that?
> 
> I remember I had many similar issues and fixed them by creating a
> simple MDA.
> 
> Best regards,
> --
>   Daniele

I created a simple pipe shell script:

#!/bin/bash
echo $LOGNAME >> /home/testlogname

I made it 777

I made /home/testlogname 666

I changed my aliases file to 

bska-archive: "| /home/bska-archive/elogname"

I sent a message. It caused the script to write 

bska-archive

into the log file./home/bska-archive/elogname
I then created another alias

supertest: "| /home/bska-archive/elogname"

supertest does not exist as a real user on the system.

It still wrote "supertest" into /home/testlogname so it is calling the
script as the user to whom the message is sent.

So, I chowned /home/bska-archive/elogname to root:lurker and chmod 770
the script and 660 the file it writes to.

Now I get a permission denied message again even though the
bska-archive user is a member of the lurker group and both files are
660 so they should be writable by the group members.

I made the writable file 666 again and it still fails. The script
MUST be 777 world writable for postfix to deliver to it.

That's ugly and shouldn't be happening.

I'm going to try one or two more things then I need to wipe the lurker
install completely and start fresh (I've hosed my database with test
entries anyway).

I was trying hard to avoid having to use yet another delivery option
like procmail. I wanted to be able to just add an alias and go.

Thanks,

Gerald