describe spool file changes for -tls_peerdn

diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index 676aa534c61609fda078c3eb355ef33469742c0f..03f4469af217587cdfcb519ce4ed72eecc9e1bb8 100644 (file)
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -49,6 +49,10 @@ NM/04 Bugzilla 1237 - fix cases where printf format usage no indicated
       Bug report from Lars Müller <lars@samba.org> (via SUSE), 
       Patch from Dirk Mueller <dmueller@suse.com>
 
+PP/13 tls_peerdn now print-escaped for spool files.
+      Observed some $tls_peerdn in wild which contained \n, which resulted
+      in spool file corruption.
+
 
 Exim version 4.77
 -----------------

diff --git a/src/README.UPDATING b/src/README.UPDATING
index 3ee3035e93461f0895c95d29182df10f27c573f9..1eb36277e39acb936350d0621514707aff57e6f4 100644 (file)
--- a/src/README.UPDATING
+++ b/src/README.UPDATING
@@ -26,6 +26,20 @@ The rest of this document contains information about changes in 4.xx releases
 that might affect a running system.
 
 
+Exim version 4.78
+-----------------
+
+ * 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
+   of values with embedded newlines, which caused spool file corruption.
+
+   If you have a corrupt spool file and you wish to recover the contents after
+   upgrading, then lock the message, replace the new-lines that should be part
+   of the -tls_peerdn line with the two-character sequence \n and then unlock
+   the message.  No tool has been provided as we believe this is a rare
+   occurence.
+
+
 Exim version 4.77
 -----------------