From: Phil Pennock Date: Wed, 23 May 2012 00:12:35 +0000 (-0400) Subject: README.UPDATING: emphasise more the LDAP issue X-Git-Tag: exim-4_80_RC5~8 X-Git-Url: https://git.exim.org/exim.git/commitdiff_plain/c2b063d407d37f6d813cdc4bc9d6a346f071a471 README.UPDATING: emphasise more the LDAP issue --- diff --git a/src/README.UPDATING b/src/README.UPDATING index e685b8ec3..a15bd418e 100644 --- a/src/README.UPDATING +++ b/src/README.UPDATING @@ -31,6 +31,7 @@ Exim version 4.80 * BEWARE backwards-incompatible changes in SSL libraries, thus the version bump. See points below for details. + Also an LDAP data returned format change. * The value of $tls_peerdn is now print-escaped when written to the spool file in a -tls_peerdn line, and unescaped when read back in. We received reports @@ -77,6 +78,12 @@ Exim version 4.80 attribute as a comma-separated list. Note the distinction from multiple attributes being returned, where each one is a name=value pair. + If you are currently splitting the results from LDAP upon a comma, then you + should check carefully to see if adjustments are needed. + + This change lets cautious folks distinguish "comma used as separator for + joining values" from "comma inside the data". + * accept_8bitmime now defaults on, which is not RFC compliant but is better suited to today's Internet. See http://cr.yp.to/smtp/8bitmime.html for a sane rationale. Those who wish to be strictly RFC compliant, or know that