clamav-freshclam not configured to start on boot

[BloodyIron]

I have a fresh install of Proxmox Mail Gateway that's a few weeks old now. And the service/daemon "clamav-freshclam" is NOT set to start automatically. This seems like an undesirable state of things, so I'm going to configure it to auto start. But does anyone know why it is like this?

 

[Stoiko Ivanov]

thanks for the report - I think this is similar to:

M

Post in thread 'Automata update spamassassin.org'

Jan 23, 2025

Hi, Maybe it helps...
In my case, i have to manually start clamav-freshclam service after every update/restart of the server. After that clamAV and spamassassin updates are made daily. It was like that since the first installation (done twice for this reason)

• Mirelkaki

We'll add a patch to enable it for pmg-installations with one of the upcoming versions.

edit: short question - how did you setup your PMG (from the ISO, on top of debian, from the container-template for PVE)?

 

[Irit]

I had the same problem. I installed PMG with the iso from your website.

 

[BloodyIron]

thanks for the report - I think this is similar to:

M

Post in thread 'Automata update spamassassin.org'

Jan 23, 2025

Hi, Maybe it helps...
In my case, i have to manually start clamav-freshclam service after every update/restart of the server. After that clamAV and spamassassin updates are made daily. It was like that since the first installation (done twice for this reason)

• Mirelkaki

We'll add a patch to enable it for pmg-installations with one of the upcoming versions.

edit: short question - how did you setup your PMG (from the ISO, on top of debian, from the container-template for PVE)?

from ISO for me

 

[Stoiko Ivanov]

Thanks for the updates!
We adapted the pmg-api postinstallation to enable clamav-freshclam (unless it's explicitly masked by the admin):
https://git.proxmox.com/?p=pmg-api.git;a=commitdiff;h=cb8e149c9c257c47763a82f35f9eed9b4d95fc7b