Gitweb:
https://git.exim.org/exim.git/commitdiff/d67ad6f989a7df6d20b661b9b5fbddd0acc048b3
Commit: d67ad6f989a7df6d20b661b9b5fbddd0acc048b3
Parent: f62743e7d634a3e4260190158a8d11558d3ed842
Author: Jeremy Harris <jgh146exb@???>
AuthorDate: Mon Jul 22 11:11:33 2024 +0100
Committer: Jeremy Harris <jgh146exb@???>
CommitDate: Mon Jul 22 11:11:33 2024 +0100
Docs: new-exec no longer used for continued-connection
---
doc/doc-docbook/spec.xfpt | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index 745794a2a..4abe2c9cb 100644
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -37320,12 +37320,8 @@ See the next section for more detail about error handling.
.cindex "SMTP" "batching over TCP/IP"
When a message is successfully delivered over a TCP/IP SMTP connection, Exim
looks in the hints database for the transport to see if there are any queued
-messages waiting for the host to which it is connected. If it finds one, it
-creates a new Exim process using the &%-MC%& option (which can only be used by
-a process running as root or the Exim user) and passes the TCP/IP socket to it
-so that it can deliver another message using the same socket. The new process
-does only those deliveries that are routed to the connected host, and may in
-turn pass the socket on to a third process, and so on.
+messages waiting for the host to which it is connected.
+If it finds one, it arranges to attempt that message on the same connection.
The &%connection_max_messages%& option of the &(smtp)& transport can be used to
limit the number of messages sent down a single TCP/IP connection.
--
## subscription configuration (requires account):
##
https://lists.exim.org/mailman3/postorius/lists/exim-cvs.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-cvs-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
