On Wed, 10 Jul 2002, Conrad Wood wrote:
> originator: uid=0 gid=0 login=root name=root
You sent a message as root. Exim is therefore privileged, whatever its
permissions and ownership.
> delivering cnw@??? as cnw using holiday_transport:
> uid=1001 gid=1001 home=/home/cnw current=/home/cnw
> auxiliary group list: <none>
> set_process_info: 30869 delivering 17SJh9-00081o-00 to cnw using holiday_transport
> holiday_transport transport entered
> taking data from transport
The transport is running as uid=1001. It calls Exim in order to create a
new message.
> Exim version 3.33 debug level 9 uid=1001 gid=1001
> Berkeley DB: Sleepycat Software: Berkeley DB 2.7.7: (08/20/99)
> Removed setuid privilege: uid=1001 gid=1001 euid=1001 egid=1001
^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^
There is the problem. Why has Exim done that, I wonder? What do you have
in the rest of your Exim configuration? In particular, what have you set
in the "security" option?
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
