From 606b8b0fbb5ee89978d3b028e42631a7b973e0c4 Mon Sep 17 00:00:00 2001 From: Jeremy Harris Date: Thu, 28 Mar 2024 21:31:00 +0000 Subject: [PATCH] Docs: say explicitly where an ACL definition ends --- doc/doc-docbook/spec.xfpt | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt index d71d3696f..f7ed7964a 100644 --- a/doc/doc-docbook/spec.xfpt +++ b/doc/doc-docbook/spec.xfpt @@ -31071,7 +31071,8 @@ option to do this.) .section "Format of an ACL" "SECID199" .cindex "&ACL;" "format of" .cindex "&ACL;" "verbs, definition of" -An individual ACL consists of a number of statements. Each statement starts +An individual ACL definition consists of a number of statements. +Each statement starts with a verb, optionally followed by a number of conditions and &"modifiers"&. Modifiers can change the way the verb operates, define error and log messages, set variables, insert delays, and vary the processing of accepted messages. @@ -31090,6 +31091,9 @@ happens then depends on the verb (and in one case, on a special modifier). Not all the conditions make sense at every testing point. For example, you cannot test a sender address in the ACL that is run for a VRFY command. +The definition of an ACL ends where another starts, +or a different configuration section starts. + .section "ACL verbs" "SECID200" The ACL verbs are as follows: -- 2.30.2