It's better if you do the following:
drwxr-x--- 2 mail mail 1024 Jul 15 01:02 /var/log/exim/
drwxr-x--- 2 mail mail 1024 Jul 14 04:51 /var/spool/exim/
-rwsr-xr-x 1 root root 419808 Jul 14 04:51 /usr/sbin/exim*
And in /etc/exim.conf:
exim_user = mail
exim_group = mail
Then exim starts as root to do what it needs to, and subsequently gives
up root and becomes mail, able to write to the proper directories.
You'll probably also want:
drwxrwxr-x 2 root mail 1024 May 1 16:27 /var/spool/mail/
so that exim can write to users' mailboxes.
--jim
%%%%%%%%%%%%%%% jim knoble %%%%%%%% jmknoble@??? %%%%%%%%%%%%%%%%%
On Wed, 15 Jul 1998, Sherwood Botsford wrote:
: Docs say that exim will create spool directories as needed.
:
: [root@rondo ~]# ls -ld /var /var/spool
: drwxr-xr-x 12 root root 1024 Jul 13 05:13 /var
: drwxr-xr-x 8 root root 1024 Jul 15 10:48 /var/spool
:
: First run:
: Leaves a new directory
: [root@rondo ~]# ls -ld /var/spool/exim
: drwxr-x--- 2 root root 1024 Jul 15 10:48 /var/spool/exim
:
:
: ****
:
: However:
:
: The following steps solve the problem.
:
: 1. chown mail /opt/exim/bin/exim
: 2. chmod u+s /opt/exim/bin/exim
: (On this system chown clears the setuid flag)
:
: 3. rm -rf /var/spool/exim
: 4. mkdir /var/spool/exim
: 5. chown mail /var/spool/exim
:
: Is this likely to get me into other trouble?
--
*** Exim information can be found at
http://www.exim.org/ ***
