Hello,
Great posts everyone, I have really learned a lot from your input and
it's very much appreciated.
> As I read it, he's looking at "random users accessing random servers"
> - eg a user connecting his phone to the guest network and it then
> accessing Gmail.
Yes, this was exactly the concep
Dave McMurtrie wrote:
> The original poster doesn't mention which IMAP server he's using.
As I read it, he's looking at "random users accessing random servers" - eg a
user connecting his phone to the guest network and it then accessing Gmail.
I really don't think it's possible to do what he wan
Yes, I was able to find the file as well. I've used the syntax in the
/var/lib/clamav/local.ign2 file recommended by Al Varnell:
BC.Multios.Exploit.CVE_2017_2816-6329916-0.{}
BC.Pdf.Exploit.CVE_2017_2818-6331913-0.{}
BC.Pdf.Exploit.CVE_2017_2862-6331914-0.{}
and that worked to block the warning.
On Thu, 27 Jul 2017, G.W. Haywood wrote:
...snipped...
The message is *already* in the user's mail box, and I'd say it should
*not* be there in your scenario, because the user can pick up the bad
mail simply by connecting other than through your gateway.
The original poster doesn't mention wh
Hello again,
On Thu, 27 Jul 2017, Beeblebrox wrote:
... I need the gateway setup to be fire-up & forget.
That's a tall order. Given that requirement you don't need to add any
more complexity than you already have, and to make scanning by ClamAV
worth doing in the first place I think you'd ne
I have been noticing the same issue. I found at least one file that was
causing the error, and was able to test with a single file, instead of
having to virus scan an entire directory tree to test.
LibClamAV Warning: [Bytecode JIT]: Bytecode run timed out, timeout flag set
LibClamAV Warning: [
Perhaps you could advise what specifics re the configuration you would like for
me to provide...
Regards
--
HardenedBSD_amd64_12-Current_RadeonKMS
Please CC my email when responding, mail from list is not delivered.
___
clamav-users mailing list
clama
