DKIM: signing with t but no x timestamp. Bug 2851

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

diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff
index 89df66ba2f9c212913e6b7033b9ef1bf6f35be22..ad385b9ecbc92a58037c1faaffae9b16736533fb 100644 (file)
--- a/doc/doc-txt/NewStuff
+++ b/doc/doc-txt/NewStuff
@@ -6,6 +6,16 @@ Before a formal release, there may be quite a lot of detail so that people can
 test from the snapshots or the Git before the documentation is updated. Once
 the documentation is updated, this file is reduced to a short list.
 
 test from the snapshots or the Git before the documentation is updated. Once
 the documentation is updated, this file is reduced to a short list.
 

+Version 4.98
+------------
+ 1. The dkim_status ACL condition may now be used in data ACLs
+
+ 2. The dkim_verbose logging control also enables logging of signing
+
+ 3. The dkim_timestamps signing option now accepts zero to include a current
+    timestamp but no extiry timestamp.  Code by Simon Arlott; testsuite
+    additions by jgh.
+

 Version 4.97
 ------------
 
 Version 4.97
 ------------
 


@@ -1190,7 +1200,7 @@ Version 4.68
 
  9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
     cases when an SMTP session ends without sending QUIT. However, when Exim
 
  9. There is a new ACL, specified by acl_smtp_notquit, which is run in most
     cases when an SMTP session ends without sending QUIT. However, when Exim

-    itself is is bad trouble, such as being unable to write to its log files,
+    itself is in bad trouble, such as being unable to write to its log files,

     this ACL is not run, because it might try to do things (such as write to
     log files) that make the situation even worse.
 
     this ACL is not run, because it might try to do things (such as write to
     log files) that make the situation even worse.