Added DISABLE_DKIM option to EDITME, leaving some breadcrumbs about it being turned...

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

diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff
index 6f912fd4dd6fc70317d32f18c3c097fdbcaa0718..b42c0d07ca2f1533aab09b7d6743fd75aad5d7bb 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.165 2010/06/03 15:20:41 jetmore Exp $
 
 New Features in Exim
 --------------------
@@ -25,26 +25,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).