Does this change how socket-connected clients (milters, for example)
communicate?
On 11/19/18 11:40 AM, Joel Esler (jesler) wrote:
# Changes to the libclamav API:
* Those who build applications around our shared library will need to change
how they declare and pass scanning options to li
I was just looking at freshclam.conf.sample in 0.101.2, and it looks
like *all* logging is disabled by default (back to 0.98.6, at least).
I wonder how many users of ClamAV actually log their freshclam updates.
Those who don't likely won't notice freshclam temporary failures due
to an out-of-sync
