[exim-dev] NewStuff 4.70 fixes

Top Page
Delete this message
Reply to this message
Author: Phil Pennock
Date:  
To: exim-dev
Subject: [exim-dev] NewStuff 4.70 fixes
NewStuff is somewhat bare in the 4.70 release. I see from CVS that the
solution chosen is to expand the 4.70 section when 4.71 comes out.

I worked through ChangeLog and the patches which, in addition, I know
went in -- but that latter category is strongly biased towards patches I
wrote. This patch adds seven items to NewStuff, four of which are based
on my patches (and one of which I was involved in the discussion for).

What else needs to go into NewStuff?

Regards,
-Phil, now looking at needing to write a doc patch for randint.
Index: NewStuff
===================================================================
RCS file: /repo/exim/exim-doc/doc-txt/NewStuff,v
retrieving revision 1.160
diff -a -u -p -r1.160 NewStuff
--- NewStuff    14 Nov 2009 20:35:55 -0000    1.160
+++ NewStuff    16 Nov 2009 13:08:48 -0000
@@ -18,6 +18,30 @@ Version 4.70


2. Experimental DCC support via dccifd (contributed by Wolfgang Breyha).

+ 3. There is now a bool{} expansion condition which maps certain strings to
+    true/false condition values (most likely of use in conjuction with the
+    and{} expansion operator).
+
+ 4. The $spam_score, $spam_bar and $spam_report variables are now available
+    at delivery time.
+
+ 5. exim -bP now supports "macros", "macro_list" or "macro MACRO_NAME" as
+    options, provided that Exim is invoked by an admin_user.
+
+ 6. There is a new option gnutls_compat_mode, when linked against GnuTLS,
+    which increases compatibility with older clients at the cost of decreased
+    security.  Don't set this unless you need to support such clients.
+
+ 7. There is a new expansion operator, ${randint:...} which will produce a
+    "random" number less than the supplied integer.  This randomness is
+    not guaranteed to be cryptographically strong, but depending upon how
+    Exim was built may be better than the most naive schemes.
+
+ 8. Exim now explicitly ensures that SHA256 is available when linked against
+    OpenSSL.
+
+ 9. The transport_filter_timeout option now applies to SMTP transports too.
+


Version 4.68
------------