On 9/23/21, G.W. Haywood via clamav-users wrote:
> Hi there,
Hi, and thanks!
>
> I would suggest that if you're investigating problems with scanning by
> clamd, which is what clamonacc uses for the scanning, then clamdscan
> might be better a better choice than clamscan for the investigations.
On Thu, 2021-09-23 at 07:36 -0400, Maarten Broekman via clamav-users
wrote:
> To further Ged's point, these signatures that are hitting are extended
> logical signatures. Phishing signatures have a very specific format
> that are either solely looking at hostnames, host prefixes, link
>
To further Ged's point, these signatures that are hitting are extended
logical signatures. Phishing signatures have a very specific format that
are either solely looking at hostnames, host prefixes, link destinations
and alternate text, and displayed hostnames (
On Thu, 2021-09-23 at 09:28 +0100, G.W. Haywood via clamav-users wrote:
>
> Why do you not want ClamAV to alert you to (what appear to me to be)
> obvious scam emails?
Because I have chosen to disable the Phishing* checks, per the ClamAV
documentation, and apparently that isn't happening. I
Hi there,
On Wed, 22 Sep 2021, dee heffemm via clamav-users wrote:
I'm trying to setup ClamAV on a host running Apache and Phusion Passenger.
After bringing up clamd and clamonacc, connecting to the Passenger app (web
browser on 443) will result in various "Daemon failed to scan" and "Not a
Hi there,
On Thu, 23 Sep 2021, Jim Popovitch via clamav-users wrote:
On September 23, 2021 3:29:02 AM UTC, "Joel Esler (jesler)"
wrote:
On Sep 22, 2021, at 22:04, Jim Popovitch via clamav-users
wrote:
ClamAV is not respecting Phishing* settings.
clamd.conf:
...
PhishingSignatures
