Nico Erfurth wrote:
> John Dalbec wrote:
>
>> Is the error message below the result of a security feature? If so, how
>> do you suggest working around it? Some features of Exim are impossible
>> to test without sending a message "for real". In my case I was testing
>> the system_filter_reply_transport and system_filter_user settings.
>> Running "exim -bF" does not report an error if the filter runs a "mail"
>> command and system_filter_reply_transport is unset.
>>
>> [jpdalbec@mail03 jpdalbec]$ exim -C tgz/configure.exim jpdalbec@???
>
> ^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^
>
>> 2003-01-29 09:51:15 Failed to create spool file
>> /usr/local/exim/spool/input//18dtYZ-0003MP-00-D: Permission denied
>> [jpdalbec@mail03 jpdalbec]$
>> Thanks,
>> John Dalbec
>
>
> AFAIK exim will not setuid(0) if an untrusted caller uses -C, so yes,
"Untrusted" is a little misleading since it suggests (to me, anyway)
that trusted_users would be allowed to use -C without triggering the
setuid protection. Of course Exim doesn't know who the trusted_users
are since it hasn't yet read the configure file. However, UTSL reveals
that root and exim are the only "trusted" callers in this context.
John
> it's a security feature :)
>
> Nico
>
>
