On 6 Jun 2017, at 3:20, rolelael wrote:
I understand , but ..
/^route_gcgw: BE/ WARN Test
is triggered now.
And is there any way with header_checks I can accomplish my if .. end
if
somehow .
No. The utility of the 'if...endif' construct in header_checks is that
it lets you optimize
On 06/06/17 03:20, rolelael wrote:
> I understand , but ..
>
> /^route_gcgw: BE/ WARN Test
>
> is triggered now.
Because that's a single-line test.
Your other test is failing because if the /route_gcgw/ condition is
triggered, you try to compare *the line that triggered it* against a
con
I understand , but ..
/^route_gcgw: BE/ WARN Test
is triggered now.
And is there any way with header_checks I can accomplish my if .. end if
somehow .
Or is it really limited and not suitable for what I'm looking to do ?
--
View this message in context:
http://postfix.1071664.n5.nab
On 6 June 2017 at 07:49, rolelael wrote:
> Hello
>
> It's me again and the header_checks is driving me crazy
>
> Mail comming from other mail system comes into postfix were header_checks
> is
> enabled
>
> The mail system adds a header :
>
> route_gcgw: BE
>
> This header is visible when the mail
Hello
It's me again and the header_checks is driving me crazy
Mail comming from other mail system comes into postfix were header_checks is
enabled
The mail system adds a header :
route_gcgw: BE
This header is visible when the mail is received
I have a header_checks file where 'again' the if s
