That's correct and AFAIK, has always been the case. clamscan configurations is accomplished during the compile stage leading to installation and clamd.conf options only apply to clamd and clamdscan.

-Al-

On Jan 8, 2020, at 18:25, Paul Kosinski via clamav-users <clamav-users@lists.clamav.net> wrote:

It seems to be because clamscan does not respect the options in clamd.conf...