It appears that my NFS mounted Maildirs are getting their forward files
treated as if they don't exist when they're locked. The end result is
that some messages are being delivered to the Inbox (skipping the
filter) instead of being queued/defered until the forward file is
unlocked (SPAM). I *think*, it's a bit hard to debug.
Reading all the FAQs and the Options index, it appears that all the
locking options pertain to the appendfile transport. According to docs
for 'file', exim only checks for a nonexistent file; it seems that if
everything is there but denied (locked?), the filter is just skipped as
if it wasn't there.
How do I get exim to stop and wait for my forward file to become
available, and quit skipping/ignoring it if locked? (if in fact the
reason it's being skipped is because of NFS lock)
userforward:
driver = redirect
check_local_user
local_part_suffix = +* : -*
local_part_suffix_optional
file = $home/forward.txt
allow_filter
directory_transport = forward_delivery
no_verify
no_expn
check_ancestor
file_transport = address_file
pipe_transport = address_pipe
reply_transport = address_reply
# FAQ_4.html#TOC156
skip_syntax_errors
syntax_errors_to = real-$local_part@$domain
syntax_errors_text = "\
This is an automatically generated message. An error has been \
found\nin your .forward file. Details of the error are reported \
below. While\nthis error persists, messages addressed to you will \
get delivered into\nyour normal mailbox and you will receive a \
copy of this message for\neach one."
thx,
-te
--
Troy Engel | Systems Engineer
Fluid, Inc |
http://www.fluid.com
