I just had a Mac OS X 10.11/ClamXav 2.8.5/ClamAV 0.98.7 user with a similar
situation. Appears to be in the US, but I need to get more information to
verify that and the results of sigtool -i:
Checking official ClamAV definitions
--
ClamAV update process
Hey folks, just closing the loop on this, unsurprisingly, this turned out
to be a problem on our side. I had forgotten but we were running a custom
build of clamav a couple of commits before the 0.98.7 release that
apparently had a signature parsing regression, upgrading to the release
commit
