On 20 Aug 2008, at 08:16, 91change wrote:
> I added chmod -R 777 /var /spool/exim
>
> also to make it work .
Thats a bit drastic. Although the file permissions should prevent
people (meaning any local user) being able to read new messages, they
can move them, delete them and create new ones directly in the queue.
They can also modify any messages that were in the queue when you
changed the permissions.
> Is there any configuration , so that 'exim' itself does change the
> ownership to exim_user ?
If exim creates the directory it set things correctly according to the
settings it has at the time. Should it find the directory already
there it assumes things are set up correctly. If the settings are
changed after the spool dir was created that can cause problems as you
are finding.
One solution is to just mv the spool dir out the way and let exim re-
create it. If there are any spool files (don't bother about db hints)
then they can be placed back in the queue after, setting ownership
correctly.
Nigel.
--
[ Nigel Metheringham Nigel.Metheringham@??? ]
[ - Comments in this message are my own and not ITO opinion/policy - ]
