Allow Routers to have multiple conditions, IF each one yields a strict bool.

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

diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff
index fb7e9528ce5772603e54f40fa2586c15ad47994f..559a9f4c0f7efa0cc24c99e28bf4054519e94290 100644 (file)
--- a/doc/doc-txt/NewStuff
+++ b/doc/doc-txt/NewStuff
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-txt/NewStuff,v 1.171 2010/06/06 01:35:41 pdp Exp $
+$Cambridge: exim/doc/doc-txt/NewStuff,v 1.173 2010/06/07 07:09:10 pdp Exp $
 
 New Features in Exim
 --------------------
@@ -63,6 +63,27 @@ Version 4.73
       control = debug/opts=+expand+acl
       control = debug/tag=.$message_exim_id/opts=+expand
 
+ 7. It has always been implicit in the design and the documentation that
+    "the Exim user" is not root.  src/EDITME said that using root was
+    "very strongly discouraged".  This is not enough to keep people from
+    shooting themselves in the foot in days when many don't configure Exim
+    themselves but via package build managers.  The security consequences of
+    running various bits of network code are severe if there should be bugs in
+    them.  As such, the Exim user may no longer be root.  If configured
+    statically, Exim will refuse to build.  If configured as ref:user then Exim
+    will exit shortly after start-up.  If you must shoot yourself in the foot,
+    then henceforth you will have to maintain your own local patches to strip
+    the safeties off.
+
+ 8. Routers now support multiple "condition" tests, IF each router yields
+    a string which the bool{} operator recognises.  Note that this is a departure
+    from normal Router "condition" truth, requiring the stricter standard of
+    "true" that ACLS use.  This might be relaxed in a future release if there
+    is sufficient demand.
+    When debugging, bear in mind that these are internally wrapped up into
+    a longer, more complicated, string.  There's a reason that the bool{}
+    logic is a dependency.
+
 
 Version 4.72
 ------------