DKIM: Project coding standards

[users/jgh/exim.git] / doc / doc-txt / experimental-spec.txt

diff --git a/doc/doc-txt/experimental-spec.txt b/doc/doc-txt/experimental-spec.txt
index 74614cd3f35e0f6670cbb05a15ee29e72bf85f95..18a5fd917d050b871e605bfa25b2af8eb2129254 100644 (file)
--- a/doc/doc-txt/experimental-spec.txt
+++ b/doc/doc-txt/experimental-spec.txt
@@ -861,6 +861,8 @@ a) variables set in events raised from transports will not
    be visible outside that transport call.
 b) acl_m variables in a server context are lost on a new connection,
    and after helo/ehlo/mail/starttls/rset commands
    be visible outside that transport call.
 b) acl_m variables in a server context are lost on a new connection,
    and after helo/ehlo/mail/starttls/rset commands

+Using an ACL expansion with the logwrite modifier can be a
+useful way of writing to the main log.

 
 
 
 
 
 


@@ -1135,10 +1137,15 @@ These options are currently defined:
 - "pass" sets the authentication password. Default is empty.
 - "port" sets the tcp port number for the proxy. Default is 1080.
 - "tmo" sets a connection timeout in seconds for this proxy. Default is 5.
 - "pass" sets the authentication password. Default is empty.
 - "port" sets the tcp port number for the proxy. Default is 1080.
 - "tmo" sets a connection timeout in seconds for this proxy. Default is 5.

-
-Proxies from the list are tried in order until
-one responds.  The timeout for the overall connection
-applies to the set of proxied attempts.
+- "pri" specifies a priority for the server within the list, higher
+  values being tried first. The default priority is 1.
+- "weight" specifies a selection bias. Within a priority set servers
+  are queried in a random fashion, weighted by this value. The default
+  value for selection bias is 1.
+
+Proxies from the list are tried according to their priority
+and weight settings until one responds.  The timeout for the
+overall connection applies to the set of proxied attempts.

 
 If events are used, the remote IP/port during a
 tcp:connect event will be that of the proxy.
 
 If events are used, the remote IP/port during a
 tcp:connect event will be that of the proxy.