Alex Miller's patch for LDAP_RES_SEARCH_REFERENCE.

[users/heiko/exim.git] / doc / doc-txt / NewStuff

diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff
index 810607a5bb545c60b26f8a61920bcd8bde221fbb..3109ea96faab3cc02de663b835ce48d16058727a 100644 (file)
--- a/doc/doc-txt/NewStuff
+++ b/doc/doc-txt/NewStuff
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-txt/NewStuff,v 1.13 2004/11/19 15:18:57 ph10 Exp $
+$Cambridge: exim/doc/doc-txt/NewStuff,v 1.21 2004/12/20 15:24:27 ph10 Exp $

 
 New Features in Exim
 --------------------
 
 New Features in Exim
 --------------------


@@ -9,14 +9,14 @@ updated when there is a relatively large batch of changes). The doc/ChangeLog
 file contains a listing of all changes, including bug fixes.
 
 
 file contains a listing of all changes, including bug fixes.
 
 

-Version 4.44
+Version 4.50

 ------------
 
  1. There is a new build-time option called CONFIGURE_GROUP which works like
     CONFIGURE_OWNER. It specifies one additional group that is permitted for
     the runtime configuration file when the group write permission is set.
 
 ------------
 
  1. There is a new build-time option called CONFIGURE_GROUP which works like
     CONFIGURE_OWNER. It specifies one additional group that is permitted for
     the runtime configuration file when the group write permission is set.
 

- 2. The "control=submission" facility has a new option /retain_sender. This
+ 2. The "control=submission" facility has a new option /sender_retain. This

     has the effect of setting local_sender_retain true and local_from_check
     false for the incoming message in which it is encountered.
 
     has the effect of setting local_sender_retain true and local_from_check
     false for the incoming message in which it is encountered.
 


@@ -108,7 +108,7 @@ Version 4.44
 
     Previously this was a syntax error.
 
 
     Previously this was a syntax error.
 

-12. There is now a new "record type" that can be specified in dnsdb lookups. It
+12. There is a new "record type" that can be specified in dnsdb lookups. It

     is "zns" (for "zone NS"). It performs a lookup for NS records on the given
     domain, but if none are found, it removes the first component of the domain
     name, and tries again. This process continues until NS records are found
     is "zns" (for "zone NS"). It performs a lookup for NS records on the given
     domain, but if none are found, it removes the first component of the domain
     name, and tries again. This process continues until NS records are found


@@ -129,7 +129,11 @@ Version 4.44
     the name servers for the high-level domains such as .com or .co.uk are not
     going to be on such a list.
 
     the name servers for the high-level domains such as .com or .co.uk are not
     going to be on such a list.
 

-13. It is now possible to specify a list of domains or IP addresses to be
+13. Another new "record type" is "mxh"; this looks up MX records just as "mx"
+    does, but it returns only the names of the hosts, omitting the priority
+    values.
+
+14. It is now possible to specify a list of domains or IP addresses to be

     looked up in a dnsdb lookup. The list is specified in the normal Exim way,
     with colon as the default separator, but with the ability to change this.
     For example:
     looked up in a dnsdb lookup. The list is specified in the normal Exim way,
     with colon as the default separator, but with the ability to change this.
     For example:


@@ -147,17 +151,30 @@ Version 4.44
     default - see 14 below), in the same way that multiple DNS records for a
     single item are handled.
 
     default - see 14 below), in the same way that multiple DNS records for a
     single item are handled.
 

-    The lookup fails only if all the DNS lookups fail. As long as at least one
-    of them yields some data, the lookup succeeds. However, if there is a
-    temporary DNS error for any of them, the lookup defers.
+    The dnsdb lookup fails only if all the DNS lookups fail. If there is a
+    temporary DNS error for any of them, the behaviour is controlled by
+    an optional keyword followed by a comma that may appear before the record
+    type. The possible keywords are "defer_strict", "defer_never", and
+    "defer_lax". With "strict" behaviour, any temporary DNS error causes the
+    whole lookup to defer. With "never" behaviour, a temporary DNS error is
+    ignored, and the behaviour is as if the DNS lookup failed to find anything.
+    With "lax" behaviour, all the queries are attempted, but a temporary DNS
+    error causes the whole lookup to defer only if none of the other lookups
+    succeed. The default is "lax", so the following lookups are equivalent:
+
+      ${lookup dnsdb{defer_lax,a=one.host.com:two.host.com}}
+      ${lookup dnsdb{a=one.host.com:two.host.com}}
+
+    Thus, in the default case, as long as at least one of the DNS lookups
+    yields some data, the dnsdb lookup succeeds.

 
 

-14. It is now possible to specify the character to be used as a separator when
+15. It is now possible to specify the character to be used as a separator when

     a dnsdb lookup returns data from more than one DNS record. The default is a
     newline. To specify a different character, put '>' followed by the new
     character at the start of the query. For example:
 
       ${lookup dnsdb{>: a=h1.test.ex:h2.test.ex}}
     a dnsdb lookup returns data from more than one DNS record. The default is a
     newline. To specify a different character, put '>' followed by the new
     character at the start of the query. For example:
 
       ${lookup dnsdb{>: a=h1.test.ex:h2.test.ex}}

-      ${lookup dnsdb{>| mx=<;m1.test.ex;m2.test.ex}}
+      ${lookup dnsdb{>| mxh=<;m1.test.ex;m2.test.ex}}

 
     It is permitted to specify a space as the separator character. Note that
     more than one DNS record can be found for a single lookup item; this
 
     It is permitted to specify a space as the separator character. Note that
     more than one DNS record can be found for a single lookup item; this


@@ -166,6 +183,57 @@ Version 4.44
     The same effect could be achieved by wrapping the lookup in ${tr...}; this
     feature is just a syntactic simplification.
 
     The same effect could be achieved by wrapping the lookup in ${tr...}; this
     feature is just a syntactic simplification.
 

+16. It is now possible to supply a list of domains and/or IP addresses to be
+    lookup up in a DNS blacklist. Previously, only a single domain name could
+    be given, for example:
+
+      dnslists = black.list.tld/$sender_host_name
+
+    What follows the slash can now be a list. As with all lists, the default
+    separator is a colon. However, because this is a sublist within the list of
+    DNS blacklist domains, it is necessary either to double the separators like
+    this:
+
+      dnslists = black.list.tld/name.1::name.2
+
+    or to change the separator character, like this:
+
+      dnslists = black.list.tld/<;name.1;name.2
+
+    If an item in the list is an IP address, it is inverted before the DNS
+    blacklist domain is appended. If it is not an IP address, no inversion
+    occurs. Consider this condition:
+
+       dnslists = black.list.tls/<;192.168.1.2;a.domain
+
+    The DNS lookups that occur are for
+
+       2.1.168.192.black.list.tld  and  a.domain.black.list.tld
+
+    Once a DNS record has been found (that matches a specific IP return
+    address, if specified), no further lookups are done. If there is a
+    temporary DNS error, the rest of the sublist of domains or IP addresses is
+    tried. The dnslists item itself defers only if none of the other DNS
+    lookups in this sublist succeeds. In other words, a successful lookup for
+    any of the items in the sublist overrides a defer for a previous item.
+
+17. The log selector queue_time_overall causes Exim to output the time spent on
+    the queue as an addition to the "Completed" message. Like queue_time (which
+    puts the queue time on individual delivery lines), the time is tagged with
+    "QT=", and it is measured from the time that the message starts to be
+    received, so it includes the reception time.
+
+18. It is now possible to use both -bF and -bf on the same command, in order to
+    test a system filter and a user filter in the same run. For example:
+
+      exim -bF /system/filter -bf /user/filter </test/message
+
+    This is helpful when the system filter adds header lines or sets filter
+    variables that are used by the user filter.
+
+19. The Exiscan patch is now merged into the main source. See src/EDITME for
+    parameters for the build.
+

 
 Version 4.43
 ------------
 
 Version 4.43
 ------------