Allan Mui wrote:
> Are you building with the latest Xcode and brew dependent packages
I installed with MacPorts and let MacPorts take care of everything.
Al Varnell wrote:
> Most error reports involve files that cannot be completely scanned, either
> because the user lacks read permission or the
Thanks for the information, I'll try the build from source route and see
where it gets me.
*Tom Ossman*
toss...@aspirevc.com | aspirevc.com | +1.717.468.0293
100 North Queen Street | Suite 300 | Lancaster, PA 17603
Engage with us on Twitter | LinkedIn
Hi there,
On Fri, 3 Jan 2020, Al Varnell via clamav-users wrote:
Logs can be made to display errors, but I’m not on my computer right
now, so can’t say off-hand what needs to be changed in order to
display them.
The OP could try:
man clamd.conf
--
73,
Ged.
Sent from my iPad
On Jan 3, 2020, at 00:32, i...@schroeffu.ch wrote:
>
>>> And report the false positive to the ClamAV team?
>>
>> All false positives from SecuriteInfo.com signatures should be sent to
>> webmas...@securiteinfo.com.
>> Thank you.
>
> As this false positive was from unofficial
>> And report the false positive to the ClamAV team?
>
> All false positives from SecuriteInfo.com signatures should be sent to
> webmas...@securiteinfo.com.
> Thank you.
As this false positive was from unofficial signatures i am going to report it to
webmas...@securiteinfo.com.
>> All good :-)
Sent from my iPad
On Jan 2, 2020, at 22:38, Michael Newman via clamav-users
wrote:
> I’ve searched and looked through the ClamAV documentation but haven’t been
> smart enough to find a definition for "Total errors:". Does anyone know what
> it means?
Most error reports involve files that
