From 179ed8c31eb8c7f767ec0ef5e2856066d366515f Mon Sep 17 00:00:00 2001
From: Jeremy Harris <jgh146exb@wizmail.org>
Date: Tue, 5 Nov 2019 21:13:41 +0000
Subject: DKIM/CHUNKING: support CHUNKING when a transport_filter is used, if
 DKIM signing is being done

---
 doc/doc-docbook/spec.xfpt | 3 +++
 doc/doc-txt/ChangeLog     | 4 ++++
 2 files changed, 7 insertions(+)

(limited to 'doc')

diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index c8b999c9f..62109e915 100644
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -24897,6 +24897,9 @@ unauthenticated. See also &%hosts_require_auth%&, and chapter
 .cindex "RFC 3030" "CHUNKING"
 This option provides a list of servers to which, provided they announce
 CHUNKING support, Exim will attempt to use BDAT commands rather than DATA.
+.new
+Unless DKIM signing is being done,
+.wen
 BDAT will not be used in conjunction with a transport filter.
 
 .option hosts_try_dane smtp "host list&!!" *
diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index 45d126ccd..f9e39d2dc 100644
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -18,6 +18,10 @@ JH/03 DKIM verification defaults no long accept sha1 hashes, to conform to
       RFC 8301.  They can still be enabled, using the dkim_verify_hashes main
       option.
 
+JH/04 Support CHUNKING from an smtp transport using a transport_filter, when
+      DKIM signing is being done.  Previously a transport_filter would always
+      disable CHUNKING, falling back to traditional DATA.
+
 
 Exim version 4.93
 -----------------
-- 
cgit v1.2.3