summaryrefslogtreecommitdiff
path: root/doc/doc-txt
diff options
context:
space:
mode:
authorPhilip Hazel <ph10@hermes.cam.ac.uk>2007-04-13 15:13:47 +0000
committerPhilip Hazel <ph10@hermes.cam.ac.uk>2007-04-13 15:13:47 +0000
commit58eb016e585187a87ade7602b2aecb2208605320 (patch)
treec0021c9485b5b1b0c0b72591ffb5b827efcb1e3d /doc/doc-txt
parent0a4e3112aeb6531661cb8d49379db4f84ff5841b (diff)
Check for lost connection or unexpected input at end of message.
Diffstat (limited to 'doc/doc-txt')
-rw-r--r--doc/doc-txt/ChangeLog12
1 files changed, 11 insertions, 1 deletions
diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index 5f1982882..4a8d41d66 100644
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.501 2007/04/12 09:00:51 ph10 Exp $
+$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.502 2007/04/13 15:13:47 ph10 Exp $
Change log file for Exim from version 4.21
-------------------------------------------
@@ -202,6 +202,16 @@ SC/03 Eximstats - V1.58 Fix to get <> and blackhole to show in edomain tables.
PH/43 Yet another patch from the Sieve maintainer.
+PH/44 I found a way to check for a TCP/IP connection going away before sending
+ the response to the final '.' that terminates a message. At this time,
+ there should not be any pending input - the client should be waiting for
+ the response. Therefore, a select() can be used: if it shows that the
+ input is "ready", there is either input waiting, or the socket has been
+ closed. Both cases are errors. (It's a bit more complicated than this
+ because of buffering, but that's the essence of it.) Previously, Exim
+ would have sent an OK response which the client would never have see.
+ This could lead to message repetition. This fix should cure that.
+
Exim version 4.66
-----------------