Dear Maintainer,

with the update to 0.101.4+dfsg-0+deb10u1 clamd frequently reports:

LibClamAV Error: pdf_find_and_extract_objs: Timeout reached in the PDF parser while extracting objects.

This has not occured before the update - thus it is surprising.

It is not clear, where to configure longer timeouts for scanning pdf.

The error should be more explicit about this.

Probably, the default timeout should also be increased.
--- data dir ---
total 257436
-rw-r--r-- 1 clamav clamav   1038848 Jul 30 07:40 bytecode.cld
-rw-r--r-- 1 clamav clamav 144665600 Sep 19 11:19 daily.cld
-rw-r--r-- 1 clamav clamav 117892267 Jun 16  2017 main.cvd
-rw------- 1 clamav clamav       256 Sep 19 11:20 mirrors.dat

Is this still there?

This comes from the pdf-part of the code because scanning a given .PDF
file takes longer than the limit. The limit is by default
   MaxScanTime 120000

is time in ms, here 120 seconds or two minutes. So it took longer than
that and then it aborted, most likely a DoS prevention where an infinite
loop would occupy the daemon forever.

The surprising part is that according to your clamd.conf you have

which means no limit, take all the time you need.

Sebastian