Vis-a-vis Heiko's note of 12/23/2006 04:46 PM:
> ...
> I propose to release exim 4.65 to fix this bug. It could be really
> harmful ...
Let me second that - in my config I have a macro:
SLACK = ${if or{{ !def:interface_address }\
{ eq{$interface_address} {INSIDE} }\
{ ={$interface_port} {BACKDOOR} }}\
{friend} {stranger} }
that I use in order to have separate ACLs for trusted and untrusted
connections without undue complexity:
acl_smtp_connect = acl_SLACK_connect
acl_smtp_helo = acl_SLACK_helo
acl_smtp_rcpt = acl_SLACK_rcpt
acl_smtp_data = acl_SLACK_data
While this used to work under 4.63, with 4.64, I get:
2006-12-27 19:22:56 H=hormel.redhat.com [209.132.177.30] temporarily
rejected connection in "connect" ACL: failed to expand ACL string
"acl_${if or{{ if{ def:received_ip_address }{0}{1} }{
eq{$received_ip_address} {172.24.4.1} }{ ={$received_port} {7151}
}}{friend} {stranger} }_connect": unknown condition "if" inside
"or{...}" condition
with 4.64.
If, as the September thread indicates this is a not a bug, but rather a
feature, can someone please tell me a simpler way to achieve the same
end without hideously complicating my config. Like Winnie-the-Pooh, I am
a bear of little brain and all my attempts to do this otherwise have failed.
--
============================= Joe Christy ==============================
------------------
http://xri.net/=joe.christy ------------------
== If I can save you any time, give it to me, I'll keep it with mine. ==
