New $recipients_list. Bug 2726

[exim.git] / doc / doc-docbook / spec.xfpt

diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index b8173a1b836773090bd95e8649d903e91d62c959..cf670ba07b13d2a191b297421fe01d3b966d1feb 100644 (file)
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -7384,7 +7384,7 @@ For example, the way to write the NIS+ query is
 .endd
 .cindex "tainted data" "in lookups"
 .new
-&*All*& tainted data used in a quoery-style lookup must be quoted
+&*All*& tainted data used in a query-style lookup must be quoted
 using a mechanism appropriate for the lookup type.
 .wen
 See chapter &<<CHAPexpand>>& for full coverage of string expansions. The quote
@@ -11802,10 +11802,11 @@ all items in the list, the overall condition is true.
 .endlist
 Note that negation of &*forany*& means that the condition must be false for all
 items for the overall condition to succeed, and negation of &*forall*& means
-that the condition must be false for at least one item. In this example, the
-list separator is changed to a comma:
+that the condition must be false for at least one item.
+
+Example:
 .code
-${if forany{<, $recipients}{match{$item}{^user3@}}{yes}{no}}
+${if forany{$recipients_list}{match{$item}{^user3@}}{yes}{no}}
 .endd
 The value of &$item$& is saved and restored while &%forany%& or &%forall%& is
 being processed, to enable these expansion items to be nested.
@@ -13404,10 +13405,20 @@ The main use of this variable is expected to be to distinguish between
 rejections of MAIL and rejections of RCPT.
 
 .tvar &$recipients$&
-This variable contains a list of envelope recipients for a message. A comma and
-a space separate the addresses in the replacement text. However, the variable
-is not generally available, to prevent exposure of Bcc recipients in
-unprivileged users' filter files. You can use &$recipients$& only in these
+.new
+.tvar &$recipients_list$&
+These variables both contain the envelope recipients for a message.
+
+The first uses a comma and a space separate the addresses in the replacement text.
+&*Note*&: an address can legitimately contain a comma;
+this variable is not intended for further processing.
+
+The second is a proper Exim list; colon-separated.
+.wen
+
+However, the variables
+are not generally available, to prevent exposure of Bcc recipients in
+unprivileged users' filter files. You can use either of them  only in these
 cases:
 
 .olist
@@ -32211,7 +32222,7 @@ If multiple header lines match, all are removed.
 There is no harm in attempting to remove the same header twice nor in removing
 a non-existent header. Further header specifiers for removal may be accumulated
 during the DATA and MIME ACLs, after which matching headers are removed
-if present. In the case of non-SMTP messages, remove speifiers are
+if present. In the case of non-SMTP messages, remove specifiers are
 accumulated during the non-SMTP ACLs, and are acted on after
 all the ACLs have run. If a message is rejected after DATA or by the non-SMTP
 ACL, there really is no effect because there is no logging of what headers