[exim] Broken pipe > MYSQL: no data found

Hi,

Exim Version: 4.96-3

I'm curios, why does the mysql modul set "No data found" when there is a
fail on the clamd pipe?

2022-10-25 07:36:45 1onCcF-002IAu-0b malware acl condition: clamd  :
unable to send file body to socket (83.x.x.x): Broken pipe
2022-10-25 07:36:45 1onCcF-002IAu-0b H=X [x.x.x.x]
X=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=no F=<YYY@YYY> temporarily
rejected after DATA: MYSQL: no data found

The pipe fail is caused IMHO by some big uncompressed TIFF files
(22MB++) in the specific email. The targeted clamd server does not even
note down, that he had an incoming message which failed, so, the
resulting email must be "very" big if the connections breaks in mid
transit.

What i like to know about is the fact, that the mysql modul also looses
it's connection to the database, which is the normal cause of "MYSQL: no
data found". As one can see, this leads to the uncontrolled exit of exim
and the temporal rejection of that mail.

IMHO, it would be better to not drop the db connection and continue with
normal progress. It would be cool, if the fail of the service in use
would be available to the acls, so they can decide if the messages gets
thru or gets finally rejected ( safty first ). Both ways finalize the
delivery of the email in one way or the other, which is good.

ATM the mail in question hangs in between and will never be successfully
delivered. Only god and some M$ admins know, how long it will stay in
the mailqueue before the sender gets a final fail notice ( if he ever
gets one ).

@Jeremy&Heiko: Can I workaround this db con problem in 4.96?

Best regards,
Marius