[exim] Spurious "BDAT command used when CHUNKING not adverti…

Top Page
Delete this message
Reply to this message
Author: Jesse Hathaway
Date:  
To: exim-users
Subject: [exim] Spurious "BDAT command used when CHUNKING not advertised"?
Just recently, starting on May 4th, we began bouncing some messages from
Gmail with the following error:

2022-05-09 15:32:48 H=mail-lj1-x234.google.com
[2a00:1450:4864:20::234]:46864 I=[2620:0:861:3:208:80:154:76]:25
X=TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256 CV=no
F=<translations+caf_=jsoby=wikimedia.org@???> rejected RCPT
<jsoby@???>: Previous (cached) callout verification failure
2022-05-09 15:32:48 SMTP protocol error in "BDAT 18952 LAST"
H=mail-lj1-x234.google.com [2a00:1450:4864:20::234]:46864
I=[2620:0:861:3:208:80:154:76]:25 BDAT command used when CHUNKING not
advertised
2022-05-09 15:32:48 SMTP syntax error in "Received: by
mail-lj1-x234.google.com with SMTP id 16so17499146lju.13"
H=mail-lj1-x234.google.com [2a00:1450:4864:20::234]:46864
I=[2620:0:861:3:208:80:154:76]:25 unrecognized command
2022-05-09 15:32:48 SMTP syntax error in "        for
<jsoby@???>; Mon, 09 May 2022 08:32:48 -0700 (PDT)"
H=mail-lj1-x234.google.com [2a00:1450:4864:20::234]:46864
I=[2620:0:861:3:208:80:154:76]:25 unrecognized command
2022-05-09 15:32:48 SMTP syntax error in "X-Google-DKIM-Signature:
v=1; a=rsa-sha256; c=relaxed/relaxed;" H=mail-lj1-x234.google.com
[2a00:1450:4864:20::234]:46864 I=[2620:0:861:3:208:80:154:76]:25
unrecognized command
2022-05-09 15:32:48 SMTP call from mail-lj1-x234.google.com
[2a00:1450:4864:20::234]:46864 I=[2620:0:861:3:208:80:154:76]:25
dropped: too many syntax or protocol errors (last command was
"X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;",
C=EHLO,STARTTLS,EHLO,MAIL,RCPT,BDAT,RSET,NOOP,MAIL,RCPT,BDAT)


We are currently running exim 4.94 on Debian. In trying to understand the root
cause of the issue I noticed a recent commit included in 4.96:

JH/26 Fix CHUNKING on a continued-transport. Previously the usabliility of the
the facility was not passed across execs, and only the first message passed
over a connection could use BDAT; any further ones using DATA.

Is this commit at all related? Is there a chance Gmail changed their sending
behavior?

Any insight is much appreciated, thanks, Jesse Hathaway