JR,
Upon looking more at the debug output, another entry in the system
filter evaluated true, and had a significant action itself and was not
going to the later bits of the system filter.
I wasn't using the filter debug flag correctly earlier, which led me
to believe it wasn't even reaching the system filter, but in fact it
is, but hitting another rule.
The rule behaved similar to the first_delivery, I add headers to the
message, and if they exist, I exit the filter for normal delivery.
Once the message passed through successfully the first time, those
headers were present in the retry, and triggered the filter to setup
normal delivery.
So this was all my fault ;)
Thank you all for looking into the issue though. I learn something new
with Exim every day, quite a flexible mailer, this is.
On Tue, Jun 8, 2010 at 1:38 AM, J.R.Haynes <J.Haynes@???> wrote:
> On Tue, 8 Jun 2010 at 04:06 +0100, Brent Jones wrote
>
>> The behavior as I understand it written on:
>> http://www.exim.org/exim-html-current/doc/html/spec_html/ch43.html
>> "The system filter is run at the start of a delivery attempt, before
>> any routing is done. If a message fails to be completely delivered at
>> the first attempt, the system filter is run again at the start of
>> every retry."
>>
>
> The sentence after that says 'If you want your filter to do something only
> once per message, you can make use of the first_delivery condition in an if
> command in the filter to prevent it happening on retries.'
>
> Have you perhaps got an if (first_delivery) around the whole filter or part
> of it?
>
>
>
>
> --
> ------------------------------------------------------------------------------
>
> J. R. Haynes
> Senior Network Specialist
>
> IT Department, e-mail: J.Haynes@???
> Bld 63,
> Cranfield University, Tel: Bedford (01234) 754205
> Wharley End, Bedford (01234) 750111 Extn 4205
> Cranfield, Fax: Bedford (01234) 751814
> Beds.,
> MK43 0AL.
>
--
Brent Jones
brent@???
