Hi Philip
Q0065 seems to be the issue for my own problems using autoreply i.e. the
spool is only writable by exim.
Personally I'm running two exim processes as follows:
/usr/exim/bin/exim -C /usr/exim/exim.in -bd
/usr/exim/bin/exim -C /usr/exim/exim.out -q15m
this allows me to pass messages through MailScanner for virus and spam
checking.
If you are using multiple configuration files (as I am) then I can't see
any obvious way around the issue - other than allowing the spools to be
writable by anyone (which I'm not about to do). Any thoughts/help would
be welcome ?
The main reason I am after autoreply is because the company I work for
would like a working vacationing system, so far we have had to do
without due to the above issues.
Regards
Simon
Philip Hazel wrote:
>On Tue, 26 Aug 2003, Jan-Peter Koopmann wrote:
>
>
>
>>>That's the problem. You need to find out why it did that.
>>>Maybe running with a higher debug level would help.
>>>
>>>
>>No it does not unfortunately. But it seems to be a permission problem.
>>Once we used the user "root" everything worked. We changed it to user
>>mailnull group mail and it again worked. Other users do not. This seems
>>to be a directory right problem of some sort. Maybe
>>/var/spool/exim/input or something like that?
>>
>>
>
>How are you running Exim? Is it setuid root? Were you calling it with
>the -C or -D options? There's a similar issue mentioned in Q0065 in the
>FAQ.
>
>--
>Philip Hazel University of Cambridge Computing Service,
>
>
