I have set up special "away/vacation" filters inside /usr/exim/away.
They look like this one:
/usr/exim/away/jkezar.away
# Exim filter
if personal then
mail
to $reply_address
subject "Re: $h_subject"
text "away"
endif
So the syntax of the file in the director is
/usr/exim/away/${local_part}.away
All the files in this directory are owned by user nobody(A user that a
CGI script can make use of)
My director looks like this:
useraway:
driver = forwardfile
file = /usr/exim/away/${local_part}.away
require_files = /usr/exim/away/${local_part}.away
user = nobody
group = nobody
no_verify
no_expn
check_ancestor
filter
file_transport = address_file
pipe_transport = address_pipe
reply_transport = address_reply
match_directory = !^/nonexistent
In the Exim error logs I am getting this when I test:
temper@??? D=useraway defer (-11): bad owner for
/usr/exim/away/temper.away
My director explicitly sets user=nobody and goup=nobody
The file perminsions on temper.away are this:
-rw-r--r-- 1 nobody nobody 97 Oct 16 08:17 temper.away
How do I tell Exim not to worry about the owner of these filters?
How can I let Exim know thay user = nobody has the right to use this
filter?
Clarified: How do I not get the "bad owner" error message?
Thanks!
--
Joseph Kezar
