@ Maarten Broekman - I'm using the version 0.103.5 which, I think, is
the current version in KDE Neon repos (KDE Neon being based on Ubuntu
20). But what I did yesterday (manual tuning of the configuration file,
lowering the number of times per day the updates are fetched and
increasing the receive timeout) helped. This evening, when I started my
computer after returning from work, I checked the version of the virus
database and saw that ClamAV had managed to update it.
@ G.W. Haywood - Hopefully after manual tweaking of the config file
everything works again as it should (as I explained in my answer to
Maarten Broekman above). And it's not that I've been neglecting the
security... It's just that as everything had been working smooth and
fine since I've installed ClamAV many years ago, I've stopped manually
checking if everything was still OK (because why would it stop working
after all those years?)... My bad.
Anyway, three things:
1. I would like to apologize for writing BEFORE I could verify if the
manual tweaks would work once my cool-down period lifted.
2. Thank you all for your patience and your help.
3. There is still one question that puzzles me: why the default
configuration of ClamAV (checking for updates every hour, Retrieve
Timeout set to 30) is designed in a way that leads directly to the ban
by the CDN and renders the software useless?
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
