pls parallels standard clamav integration!

Please !

I need ClamAV to secure a NextCloud installation.

ClamAV is needed into Plesk!

How long more?

please

Yes Please

i also vote for a clamav integration in a free extension!

ClamAv Pleeeaaasseeeeee.
seriously, competition offers the means to deploy it when they are less expensive. Where does the problem ?
A request for 4 years already.not understand this non position statement. Do we deserve this treatment ? We put money so take a stand.

Plesk Team, why don't you close this one? You already have your paid extension.

ClamAV Now!

Found this uservoice on the search for a ClamAV support, voted for this feature!

ClamAV should be a free extension for scanning the web server traffic not just email, and why should it be paid when its a free product.

Thank you for link!

Looking at the fact that Plesk Email Security Pro now includes ClamAV, I assume from a change request point of view, Plesk will see this as solved.
However, it is VERY DISAPPOINTING to see again that Plesk failed to follow the community demand having this as an unpaid extension.
Also, from a security standpoint, I think it is socially not acceptable that they require us to pay for it, especially given the fact that they mainly employ open software for this feature.
In addition, the extension has the drawback that greylisting needs to be disabled, which I think is a bad idea.

Nevertheless, following https://www.lloyd-day.me/migrate-plesk-to-clamav/, there is quite a simple solution if you want to integrate ClamAV yourself.
By not uninstalling DrWeb (free protection of 10 mailboxes), you can even run both in parallel by adapting the information in step 4 (settings for /etc/postfix/main.cf):

With psa_remote and ClamAV, I use:
smtpd_milters = {inet:127.0.0.1:12768, default_action=accept}, { inet:127.0.0.1:3381, protocol=6, default_action=tempfail }
non_smtpd_milters = , inet:127.0.0.1:12768

This setting also helps to avoid issues when DrWeb fails to scan e-mails (happens quite frequently)...

@Dirk I'm sorry, there are too many useless comments.

I think the Plesk's direction is clear: Ok ClamAV, but in a paid and comprehensive feature.

@Ivo
You obviously haven't understood at all what this request is all about.
It wouldn't hurt if you read the comments below to get the full picture.

Feature released: https://www.plesk.com/plesk-email-security/

.. but it's a paid feature...

I think this request can be considered as closed

Here are my thoughts about this:

Plesk should have a contract with the current non-free AVs for some years. And on that contract
should be a clause about not adding a free AV.

Plesk receives money for each license it sells.

@thomas: and how about e.g. postfix? apache? etc.?

However, issuers of alternative proprietary payable services should strive to make their products "better" than their OS "competition", enough to justify licensing it.

And Plesk should provide more sophisticated/flexible integration with more options per user. From what I saw last time when I checked it, Alleged sender addresses are notified about each detected malware sent in their name??? Honestly??? And then there's no quarantineing (they could e.g. create and use a mailbox subfolder for that, accessible for release by the user itself anytime, just as they do with spam together with assassin). And then it's all about mail's content only, hyperlinks are not scanned. As long as such design flaws persist, then I'm not going to provide AV to the users on my plesked systems. Not even ClamAV, if it'd have the same flaws there.

Users need to think before clicking/opening anyway, even if any AV is enabled for assistance, be it locally or anywhere in the network.