[exim-cvs] README.UPDATING: emphasise more the LDAP issue

Gitweb: http://git.exim.org/exim.git/commitdiff/c2b063d407d37f6d813cdc4bc9d6a346f071a471

Commit:     c2b063d407d37f6d813cdc4bc9d6a346f071a471
Parent:     98a3b5270f8d5c172d26a407dbf7405755b4e976
Author:     Phil Pennock <pdp@???>
AuthorDate: Tue May 22 20:12:35 2012 -0400
Committer:  Phil Pennock <pdp@???>
CommitDate: Tue May 22 20:12:35 2012 -0400

    README.UPDATING: emphasise more the LDAP issue
---
 src/README.UPDATING |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/src/README.UPDATING b/src/README.UPDATING
index e685b8e..a15bd41 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