Deal with anonymous SSL giving us no peer certificate.

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

diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff
index 6f912fd4dd6fc70317d32f18c3c097fdbcaa0718..c2c49379f6a68a1d9da72d954eb2c76aa62cfd8d 100644 (file)
--- a/doc/doc-txt/NewStuff
+++ b/doc/doc-txt/NewStuff
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-txt/NewStuff,v 1.163 2010/06/01 11:13:54 pdp Exp $
+$Cambridge: exim/doc/doc-txt/NewStuff,v 1.167 2010/06/05 10:04:43 pdp Exp $
 
 New Features in Exim
 --------------------
@@ -9,6 +9,24 @@ test from the snapshots or the CVS before the documentation is updated. Once
 the documentation is updated, this file is reduced to a short list.
 
 
+Version 4.73
+------------
+
+ 1. A new main configuration option, "openssl_options", is available if Exim
+    is built with SSL support provided by OpenSSL.  The option allows
+    administrators to specify OpenSSL options to be used on connections;
+    typically this is to set bug compatibility features which the OpenSSL
+    developers have not enabled by default.  There may be security
+    consequences for certain options, so these should not be changed
+    frivolously.
+
+ 2. A new pipe transport option, "permit_coredumps", may help with problem
+    diagnosis in some scenarios.  Note that Exim is typically installed as
+    a setuid binary, which on most OSes will inhibit coredumps by default,
+    so that safety mechanism would have to be overriden for this option to
+    be able to take effect.
+
+
 Version 4.72
 ------------
 
@@ -25,26 +43,28 @@ Version 4.72
     in the presence of multiple character strings within the RR. Prior to 4.70,
     only the first string would be returned.  The dnsdb lookup now, by default,
     preserves the pre-4.70 semantics, but also now takes an extended output
-    separator specification. The first output separator is used to join
-    multiple TXT records together; use a second separator character, followed
-    by a colon, to join the strings within a TXT record on that second
-    character, or use a semicolon to concatenate strings within a TXT record
-    with no separator.  Administrators are reminded that DNS provides no
-    ordering guarantees between multiple records in an RRset.  For example:
+    separator specification.  The separator can be followed by a semicolon, to
+    concatenate the individual text strings together with no join character,
+    or by a comma and a second separator character, in which case the text
+    strings within a TXT record are joined on that second character.
+    Administrators are reminded that DNS provides no ordering guarantees
+    between multiple records in an RRset.  For example:
 
       foo.example.  IN TXT "a" "b" "c"
       foo.example.  IN TXT "d" "e" "f"
 
       ${lookup dnsdb{>/ txt=foo.example}}   -> "a/d"
       ${lookup dnsdb{>/; txt=foo.example}}  -> "def/abc"
-      ${lookup dnsdb{>/+: txt=foo.example}} -> "a+b+c/d+e+f"
+      ${lookup dnsdb{>/,+ txt=foo.example}} -> "a+b+c/d+e+f"
 
-    Some character combinations are currently unsupported.
 
 Version 4.70 / 4.71
 -------------------
 
  1. Native DKIM support without an external library.
+    (Note that if no action to prevent it is taken, a straight upgrade will
+    result in DKIM verification of all signed incoming emails.  See spec
+    for details on conditionally disabling)
 
  2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).