From 796718d6133b8f3b868e09f22dbdcbd8bcdad10c Mon Sep 17 00:00:00 2001 From: Jeremy Harris Date: Tue, 27 Dec 2016 16:47:36 +0000 Subject: [PATCH] Docs: clarify headers availability in data-time ACLs --- doc/doc-docbook/spec.xfpt | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt index ced906eaa..2acd5d38e 100644 --- a/doc/doc-docbook/spec.xfpt +++ b/doc/doc-docbook/spec.xfpt @@ -9417,12 +9417,19 @@ message, and any that are added by an ACL statement or by a system filter. Header lines that are added to a particular copy of a message by a router or transport are not accessible. -For incoming SMTP messages, no header lines are visible in ACLs that are obeyed -before the DATA ACL, because the header structure is not set up until the -message is received. Header lines that are added in a RCPT ACL (for example) +For incoming SMTP messages, no header lines are visible in +.new +ACLs that are obeyed before the data phase completes, +.wen +because the header structure is not set up until the message is received. +They are visible in DKIM, PRDR and DATA ACLs. +Header lines that are added in a RCPT ACL (for example) are saved until the message's incoming header lines are available, at which -point they are added. When a DATA ACL is running, however, header lines added -by earlier ACLs are visible. +point they are added. +.new +When any of the above ACLs ar +.wen +running, however, header lines added by earlier ACLs are visible. Upper case and lower case letters are synonymous in header names. If the following character is white space, the terminating colon may be omitted, but -- 2.30.2