Am I wrong, or doesn't fail act as a significant delivery, preventing
further processing? By its very name fail implies a terminal action. log,
save, fail seems a logical order to me. You say that no-where is this
documented. Try looking in the Exim specification (section 47.2 "Additional
commands for system filters"):
"The interpretation of a system filter file ceases after a freeze or fail
command is obeyed. However, any deliveries that were set up earlier in the
filter file are honoured, so you can use a sequence such as
mail ...
freeze
to send a specified message when the system filter is freezing (or failing)
something. The normal deliveries for the message do not, of course, take
place. "
Paul
-----Original Message-----
From: Greg Ward [
mailto:gward@mems-exchange.org]
Sent: 19 September 2001 14:50
To: exim-users@???
Subject: Re: [Exim] a quickie on filter command orders
On 19 September 2001, Tamas TEVESZ said:
> if i have commands in this order:
>
> save /var/mail/rejected_messages/nimda/
> fail text "whatever\n"
>
> then it's fine. however, if ordered like this:
>
> fail text "whatever\n"
> save /var/mail/rejected_messages/nimda/
>
> then the "save" has no effect at all. doesn't show up in logs, doesn't
> save obviosly, doesn't do nothing (it "fail"s all right, though).
If it's any consolation, you're not hallucinating. I had the very same
problem when I setup virus filtering to log, reject, and save viral
messages. It only worked if I did them in a particular order: save,
log, send rejection message. Nowhere did I see this documented, and
nothing in the logs indicated that the "save" command was ignored if it
didn't come first. But that seems to have been what was happening.
Greg
--
Greg Ward - software developer gward@???
MEMS Exchange http://www.mems-exchange.org
--
## List details at
http://www.exim.org/mailman/listinfo/exim-users Exim
details at
http://www.exim.org/ ##
