Docs: add note on Received-By: header creation under cutthrough

diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index 669248c116cbe9ef59b4771547f1f216976e6dbf..5b735907ed012e7d914ce6f0b44f43eedfb13a38 100644 (file)
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -29014,6 +29014,11 @@ and cannot depend on content of received headers.
 Note also that headers cannot be
 modified by any of the post-data ACLs (DATA, MIME and DKIM).
 Headers may be modified by routers (subject to the above) and transports.
+.new
+The Received-By: header is generated as soon as the body reception starts,
+rather than the traditional time after the full message is received;
+this will affect the timestamp.
+.wen
 
 All the usual ACLs are called; if one results in the message being
 rejected, all effort spent in delivery (including the costs on

diff --git a/src/src/receive.c b/src/src/receive.c
index 28da47f838b0126ed4948d0dec48048e92ed27f9..f8320bd2059117064f5a8db0d90e097b15c88573 100644 (file)
--- a/src/src/receive.c
+++ b/src/src/receive.c
@@ -3027,7 +3027,6 @@ if (chunking_state > CHUNKING_OFFERED)
 /* Cutthrough delivery:
 We have to create the Received header now rather than at the end of reception,
 so the timestamp behaviour is a change to the normal case.
-XXX Ensure this gets documented XXX.
 Having created it, send the headers to the destination. */
 
 if (cutthrough.fd >= 0 && cutthrough.delivery)