• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Issue Error installing ClamAV in Plesk Email Security on AlmaLinux 10

jnthn

New Pleskian
Server operating system version
AlmaLinux 10.1
Plesk version and microupdate number
18.0.77
I installed Plesk Email Security on my AlmaLinux 10 server and activated a paid license. Then I attempted to install ClamAV, but it fails with the following error:
Execution yum has failed with exit code 1, stdout: Extra Packages for Enterprise Linux 10 - Testin 523 kB/s | 113 kB 00:00
No match for argument: clamsmtp
, stderr: Error: Unable to find a match: clamsmtp

I already found these related topics and articles about a previous similar issue on AlmaLinux 9:
However, according to the Plesk Email Security changelog it should support AlmaLinux 10:
1.5.19 (19 June 2025)
[+] Added support for AlmaLinux 10.

What should I do now? I have paid for the extension license and would like to start using it soon.
 
P.S. It's a 'clean' server. I installed Plesk about a month ago; at that time the server was fresh installed with AlmaLinux 10.
 
Hi, @jnthn . Thank you for reporting the issue. I was able to replicate the behavior on AlmaLinux 10 and opened an internal case for further investigation by our developers. Thank you in advance for your understanding on the matter.
 
Last edited:
@Sebahat.hadzhi Thank you for your fast response!

Could you ask your developers to confirm whether the workaround from the article is safe to apply with the current extension version on AlmaLinux 10? I'm not really comfortable running a 2 year old workaround for a previous OS version on my server.
 
@jnthn , I spoke too soon. Although the service can be installed with the workaround it won't start. Apologies about that. I will follow-up with a workaround as soon as possible.
 
Back
Top