X-Git-Url: https://vcs.fsf.org/?p=exim.git;a=blobdiff_plain;f=src%2FREADME.UPDATING;h=b5630d3099f36431f8b91e65203f7fb4b3ed6d74;hp=b83ca2ab48f1b55e786d1246243ca9e8aebb8b0a;hb=f3f0a1f0ea2e1b74620b99c6055a12b1b688f808;hpb=b5aea5e16720f8b17bcbbf54af966ba034432db9

diff --git a/src/README.UPDATING b/src/README.UPDATING
index b83ca2ab4..b5630d309 100644
--- a/src/README.UPDATING
+++ b/src/README.UPDATING
@@ -1,4 +1,4 @@
-$Cambridge: exim/src/README.UPDATING,v 1.5 2005/03/08 11:38:21 ph10 Exp $
+$Cambridge: exim/src/README.UPDATING,v 1.8 2005/09/14 13:20:12 ph10 Exp $
 
 This document contains detailed information about incompatibilities that might
 be encountered when upgrading from one release of Exim to another. The
@@ -28,11 +28,18 @@ The rest of this document contains information about changes in 4.xx releases
 that might affect a running system.
 
 
+Version 4.53
+------------
+
+If you are using the experimental Domain Keys support, you must upgrade to
+at least libdomainkeys 0.67 in order to run this release of Exim.
+
+
 Version 4.51
 ------------
 
-The format in which GnuTLS parameters are cached (in the file gnutls-params in
-the spool directory) has been changed. The new format can also be generated
+1. The format in which GnuTLS parameters are cached (in the file gnutls-params
+in the spool directory) has been changed. The new format can also be generated
 externally, so it is now possible to update the values from outside Exim. This
 has been implemented in an upwards, BUT NOT downwards, compatible manner.
 Upgrading should be seamless: when Exim finds that it cannot understand an
@@ -41,6 +48,19 @@ in the new format. If, however, you downgrade from 4.51 to a previous release,
 you MUST delete the gnutls-params file in the spool directory, because the
 older Exim will not recognize the new format.
 
+2. When doing a callout as part of verifying an address, Exim was not paying
+attention to any local part prefix or suffix that was matched by the router
+that accepted the address. It now behaves in the same way as it does for
+delivery: the affixes are removed from the local part unless
+rcpt_include_affixes is set on the transport. If you have a configuration that
+uses prefixes or suffixes on addresses that could be used for callouts, and you
+want the affixes to be retained, you must make sure that rcpt_include_affixes
+is set on the transport.
+
+3. Bounce and delay warning messages no longer contain details of delivery
+errors, except for explicit messages (e.g. generated by :fail:) and SMTP
+responses from remote hosts.
+
 
 Version 4.50
 ------------