==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.3.1
- Deployed with iRedMail Easy or the downloadable installer? Installer
- Linux/BSD distribution name and version: CentOS 8 Basic
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MariaDB
- Web server (Apache or Nginx):Nginx
- Manage mail accounts with iRedAdmin-Pro?No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

There seem to be several recent posts about changes to / failures of ClamAV.
See e.g. this and this.

I'm starting a separate thread because, although it is likely related to the others, it's a different symptom and may in fact be the source of some of the other issues.

I was doing a regular security update to the OS this morning and noticed the following fly by:

  Upgrading        : grub2-tools-minimal-1:2.02-90.el8_3.1.x86_64          4/70
  Running scriptlet: clamav-filesystem-0.103.1-3.el8.noarch                5/70
  Upgrading        : clamav-filesystem-0.103.1-3.el8.noarch                5/70
  Upgrading        : clamav-lib-0.103.1-3.el8.x86_64                       6/70
  Upgrading        : clamav-update-0.103.1-3.el8.x86_64                    7/70
  Running scriptlet: clamav-update-0.103.1-3.el8.x86_64                    7/70
Warning: clamav-update package changed
Now we provide clamav-freshclam.service systemd unit instead old scripts and the cron.d entry.
Unfortunately this may break existing unattended installations.
Please run 'systemctl enable clamav-freshclam --now' to enable freshclam updates again.

  Upgrading        : grub2-tools-extra-1:2.02-90.el8_3.1.x86_64            8/70

Is this bad? Shall I run the enable command as they say? Do I need to do anything else?