diff options
author | Phil Pennock <pdp@exim.org> | 2012-05-25 10:29:06 -0400 |
---|---|---|
committer | Phil Pennock <pdp@exim.org> | 2012-05-25 10:29:06 -0400 |
commit | a9bade1bafed6b15f68ad49ab45e2e343a853079 (patch) | |
tree | b893b97134a93a3a3f899c117abbafd5d60fd1d2 | |
parent | 16880d1a95a51a8b57692b216512e8cbb7cc917d (diff) |
Doc: Provide context for bare numbers from CHAP/SECT.
-rw-r--r-- | doc/doc-docbook/spec.xfpt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt index 75a5ac02c..9eaf9e804 100644 --- a/doc/doc-docbook/spec.xfpt +++ b/doc/doc-docbook/spec.xfpt @@ -6026,16 +6026,16 @@ that it implements the details of the specific authentication mechanism, i.e. PLAIN or LOGIN. The &%server_advertise_condition%& setting controls when Exim offers authentication to clients; in the examples, this is only when TLS or SSL has been started, so to enable the authenticators you also -need to add support for TLS as described in &<<SECTdefconfmain>>&. +need to add support for TLS as described in section &<<SECTdefconfmain>>&. The &%server_condition%& setting defines how to verify that the username and password are correct. In the examples it just produces an error message. To make the authenticators work, you can use a string expansion -expression like one of the examples in &<<CHAPplaintext>>&. +expression like one of the examples in chapter &<<CHAPplaintext>>&. Beware that the sequence of the parameters to PLAIN and LOGIN differ; the -usercode and password are in different positions. &<<CHAPplaintext>>& -covers both. +usercode and password are in different positions. +Chapter &<<CHAPplaintext>>& covers both. .ecindex IIDconfiwal |