My assumption was correct, I found this blurb in the documentation
<
http://www.exim.org/exim-html-current/doc/html/spec_html/ch-generic_options_for_routers.html>
on
routers.
*New header lines are not actually added until the message is in the
process of being transported. This means that references to header lines in
string expansions in the transport’s configuration do not “see” the added
header lines. *
So back to my original question... What can I do in a router that I can
then read as a condition of another router?
On Fri, Aug 11, 2017 at 10:20 AM, Rob Gunther <redrob@???> wrote:
> I have a router that I use for catch-all purposes. If the conditions are
> all valid, it adds a header and redirects the message to the catch-all
> account defined for the domain.
>
> headers_add = "X-Catch-All: user@???"
>
> That works fine, has been working for years.
>
> Further down in my router list I am trying to add a new router, that I do
> *not* want to run if the message has the X-Catch-All header.
>
> I basically want something like this (but have not gotten it work).
>
> condition = ${if !def:h_x-catch-all:}
>
> Since I have not been able to get it work, I am assuming the header is not
> actually added yet when passing through the 2nd router.
>
> What can I do in the 1st router, that would allow me to exclude the
> message from being processed in the 2nd router?
>
>
> Rob
>
