-$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.479 2007/02/14 14:59:01 ph10 Exp $
+$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.480 2007/02/14 15:33:40 ph10 Exp $
Change log file for Exim from version 4.21
-------------------------------------------
SC/02 Applied Daniel Tiefnig's patch to improve the '($parent) =' pattern match.
+PH/26 Added a "continue" ACL modifier that does nothing, for the benefit of its
+ expansion side effects.
+
Exim version 4.66
-----------------
-$Cambridge: exim/doc/doc-txt/NewStuff,v 1.141 2007/02/14 14:59:01 ph10 Exp $
+$Cambridge: exim/doc/doc-txt/NewStuff,v 1.142 2007/02/14 15:33:40 ph10 Exp $
New Features in Exim
--------------------
option; with -I they don't. In both cases it is possible to change the case
sensitivity within the pattern using (?i) or (?-i).
-14. A number of new features have been added to string expansions to make it
+16. A number of new features have been added to string expansions to make it
easier to process lists of items, typically addresses. These are as
follows:
At the end of a ${reduce expansion, the values of $item and $value is
restored to what they were before.
+17. There's a new ACL modifier called "continue". It does nothing of itself,
+ and processing of the ACL always continues with the next condition or
+ modifier. It is provided so that the side effects of expanding its argument
+ can be used. Typically this would be for updating a database. It is really
+ just a syntactic tidiness, because the following two lines have the same
+ effect:
+
+ continue = <some expansion>
+ condition = ${if eq{0}{<some expansion>}{true}{true}}
+
Version 4.66
------------
-/* $Cambridge: exim/src/src/acl.c,v 1.73 2007/02/07 11:24:56 ph10 Exp $ */
+/* $Cambridge: exim/src/src/acl.c,v 1.74 2007/02/14 15:33:40 ph10 Exp $ */
/*************************************************
* Exim - an Internet mail transport agent *
ACLC_BMI_OPTIN,
#endif
ACLC_CONDITION,
+ ACLC_CONTINUE,
ACLC_CONTROL,
#ifdef WITH_CONTENT_SCAN
ACLC_DECODE,
#endif
ACLC_VERIFY };
-/* ACL conditions/modifiers: "delay", "control", "endpass", "message",
-"log_message", "log_reject_target", "logwrite", and "set" are modifiers that
-look like conditions but always return TRUE. They are used for their side
-effects. */
+/* ACL conditions/modifiers: "delay", "control", "continue", "endpass",
+"message", "log_message", "log_reject_target", "logwrite", and "set" are
+modifiers that look like conditions but always return TRUE. They are used for
+their side effects. */
static uschar *conditions[] = {
US"acl",
US"bmi_optin",
#endif
US"condition",
+ US"continue",
US"control",
#ifdef WITH_CONTENT_SCAN
US"decode",
TRUE, /* bmi_optin */
#endif
TRUE, /* condition */
+ TRUE, /* continue */
TRUE, /* control */
#ifdef WITH_CONTENT_SCAN
TRUE, /* decode */
TRUE, /* bmi_optin */
#endif
FALSE, /* condition */
+ TRUE, /* continue */
TRUE, /* control */
#ifdef WITH_CONTENT_SCAN
FALSE, /* decode */
FALSE /* verify */
};
-/* Bit map vector of which conditions are not allowed at certain times. For
-each condition, there's a bitmap of dis-allowed times. For some, it is easier
-to specify the negation of a small number of allowed times. */
+/* Bit map vector of which conditions and modifiers are not allowed at certain
+times. For each condition, there's a bitmap of dis-allowed times. For some, it
+is easier to specify the negation of a small number of allowed times. */
static unsigned int cond_forbids[] = {
0, /* acl */
0, /* condition */
+ 0, /* continue */
+
/* Certain types of control are always allowed, so we let it through
always and check in the control processing itself. */
*log_msgptr = string_sprintf("invalid \"condition\" value \"%s\"", arg);
break;
+ case ACLC_CONTINUE: /* Always succeeds */
+ break;
+
case ACLC_CONTROL:
control_type = decode_control(arg, &p, where, log_msgptr);
deny message = domain explicitly denied
log_message = DOMAIN EXPLICITLY DENIED
+ continue = this value is not used
domains = deny.test.ex
accept domains = +local_domains
>>> test.ex in "!wontpass"? yes (end of list)
>>> require: condition test succeeded
>>> processing "deny"
+>>> check continue = this value is not used
>>> check domains = deny.test.ex
>>> test.ex in "deny.test.ex"? no (end of list)
>>> deny: condition test failed
>>> z in "!wontpass"? yes (end of list)
>>> require: condition test succeeded
>>> processing "deny"
+>>> check continue = this value is not used
>>> check domains = deny.test.ex
>>> z in "deny.test.ex"? no (end of list)
>>> deny: condition test failed
>>> test.ex in "!wontpass"? yes (end of list)
>>> require: condition test succeeded
>>> processing "deny"
+>>> check continue = this value is not used
>>> check domains = deny.test.ex
>>> test.ex in "deny.test.ex"? no (end of list)
>>> deny: condition test failed
>>> test.ex in "!wontpass"? yes (end of list)
>>> require: condition test succeeded
>>> processing "deny"
+>>> check continue = this value is not used
>>> check domains = deny.test.ex
>>> test.ex in "deny.test.ex"? no (end of list)
>>> deny: condition test failed
>>> relay.test.ex in "!wontpass"? yes (end of list)
>>> require: condition test succeeded
>>> processing "deny"
+>>> check continue = this value is not used
>>> check domains = deny.test.ex
>>> relay.test.ex in "deny.test.ex"? no (end of list)
>>> deny: condition test failed
>>> deny.test.ex in "!wontpass"? yes (end of list)
>>> require: condition test succeeded
>>> processing "deny"
+>>> check continue = this value is not used
>>> check domains = deny.test.ex
>>> deny.test.ex in "deny.test.ex"? yes (matched "deny.test.ex")
>>> deny: condition test succeeded
>>> refuse.test.ex in "!wontpass"? yes (end of list)
>>> require: condition test succeeded
>>> processing "deny"
+>>> check continue = this value is not used
>>> check domains = deny.test.ex
>>> refuse.test.ex in "deny.test.ex"? no (end of list)
>>> deny: condition test failed