Several reasons for the inclusion of ClamAV (which are important for my company):
1. We already have an infrastructure service with the central repository signatures ClamAV. If Plesk will maintain ClamAV out of the box, we can simply plug it into our infrastructure
2. ClamAV is free and is open source
3. In the event of a plurality of false-positives hosting provider will be able to remove poor-quality signature itself and will not bother its users erroneous notifications
4. We have scripts to scan files using ClamAV, that uploaded via ftp, and subsequent notification for users (at the end of the session ftp).
Several reasons for the inclusion of ClamAV (which are important for my company):
1. We already have an infrastructure service with the central repository signatures ClamAV. If Plesk will maintain ClamAV out of the box, we can simply plug it into our infrastructure
2. ClamAV is free and is open source
3. In the event of a plurality of false-positives hosting provider will be able to remove poor-quality signature itself and will not bother its users erroneous notifications
4. We have scripts to scan files using ClamAV, that uploaded via ftp, and subsequent notification for users (at the end of the session ftp).