Public SourceMage Discussion List

[nealbirch <nealbirch AT attbi.com>]

M.L. wrote:
> On Mardi 17 Décembre 2002 02:26, nealbirch wrote:
>
> > Eric Sandall wrote:
> >
> > > nealbirch said:
> > >
> > > > well, mine don't. annoying. I just did

it does now. =)

> > > > chown -R exim:exim /var/spool/mail*
> > > >
> > > > though. What did you do to change mail ownership?
> > > >
> > > > neal
> > >
> > > Well, I changed all the directories, including mail in /var/spool/mail to
> > > exim.exim, and the groups to exim on files (not the owners, as those
> > > belong to the users).  
> >
> > I hadn't setup the ownership on my individual accounts right. Thanks!
> >
> > I went to exim.org and read the faq, too. There is a good bit of
> > information there.
> >
> > Actually, now everything is running smoother than before. Wonder why the
> > change in exim, anyway.
>
> As far as I remember, I added the exim user ownership because it was 
> recomended in exim documentation... and we try to keep spells as close as the 
> authors wants them.
>
> If it is bullshit, open a bug, I'll add a query in CONFIGURE to ask whether 
> you wan to run exim as mail or as exim.

Hmmm.. now it works, after I changed the permissions properly.

I wonder if it would just be better to add something to BUILD or 
POST_INSTALL to change the permissions? That might be kinda tricky as 
you would have to chown the directory and it's contents, then chown the 
users files with the individual permissions of the users. (I'd say have 
it send an email with the fix, but emails hosed without the fix.)

neal

--
"You can fool some of the people all of the time
--and those are the ones you have to concentrate on!"
GW Bush-- from the N.Y. Times