1170 votes and not implemented yet. Since 2013…

Another long standing plesk user about to cancel 4 server licenses. Been waiting too long for this very important feature with no response from plesk.

Please, add this feature, this is very important. Thank you!

Please, add this feature this is very important

We have also migrated and splitter Mailserver and Webserver to another System. After waiting for years without any change and response, time has come to make a decision.
Poor, really poor from Plesk

We have now migrated all our clients systems away, as there is no hope for this fundamental feature being added.

With lots of smaller users, it is just not worth paying for this feature per adress.

We ended up splitting web and mail services for our customers, but I totally understand that not every one is able to do that.

Such a shame, this was our main critique for many years.

In the end we gained much needed security and made everything significantly cheaper after migrating.

it's only 9 years we wait for this feature.... Thanks in advance.

+1

Warum wird Sicherheit in Plesk so vernachlässigt. Dieses fehlende Feature unterstützt nur die Internet-Kriminellen. Schade!

Es necesario e importante para plataforma Moodle

It won't be implemented because they sell a "pro" version of one of their extensions that implements this.

They don't have enough with the already expensive montly quote, they need more money at the expense of their users' email server security.

Their greed has no limits, specially considering we are talking about an open source component here.

So devs... Plesk users have voted on this since 2013 we are now in 2022 = 9 years!

When will we see this being implemented?

This is the 2nd most voted Ideal for Plesk that the users are asking for!

Please, add this feature this is very important

Ja bitte!

Yes please

Hi,

I'm a user and not of Plesk support.

CalmAV is to the best of my understanding enabled on Plesk for Plesk hosted mail protection:
https://www.plesk.com/blog/guides/how-to-protect-email-servers-against-spam-viruses/

I have implemented CalmAV manually to scan uploaded files, using ModSecurity as base technology.

inspectFile
Description: Executes an external program for every variable in the target list. The contents of the variable is provided to the script as the first parameter on the command line. The program must be specified as the first parameter to the operator. As of version 2.5.0, if the supplied program filename is not absolute, it is treated as relative to the directory in which the configuration file resides. Also as of version 2.5.0, if the filename is determined to be a Lua script (based on its .lua extension), the script will be processed by the internal Lua engine. Internally processed scripts will often run faster (there is no process creation overhead) and have full access to the transaction context of ModSecurity.

The @inspectFile operator was initially designed for file inspection (hence the name), but it can also be used in any situation that requires decision making using external logic.

The OWASP ModSecurity Core Rule Set (CRS) includes a utility script in the /util directory called runav.pl ModSecurity that allows the file approval mechanism to integrate with the ClamAV virus scanner. This is especially handy to prevent viruses and exploits from entering the web server through file upload.

#!/usr/bin/perl
#
# runav.pl
# Copyright (c) 2004-2011 Trustwave
#
# This script is an interface between ModSecurity and its
# ability to intercept files being uploaded through the
# web server, and ClamAV

$CLAMSCAN = "clamscan";

if ($#ARGV != 0) {
print "Usage: runav.pl <filename>\n";
exit;
}

my ($FILE) = shift @ARGV;

$cmd = "$CLAMSCAN --stdout --no-summary $FILE";
$input = `$cmd`;
$input =~ m/^(.+)/;
$error_message = $1;

$output = "0 Unable to parse clamscan output [$1]";

if ($error_message =~ m/: Empty file\.?$/) {
$output = "1 empty file";
}
elsif ($error_message =~ m/: (.+) ERROR$/) {
$output = "0 clamscan: $1";
}
elsif ($error_message =~ m/: (.+) FOUND$/) {
$output = "0 clamscan: $1";
}
elsif ($error_message =~ m/: OK$/) {
$output = "1 clamscan: OK";
}

print "$output\n";

Example: Using the runav.pl script:

# Execute external program to validate uploaded files
SecRule FILES_TMPNAMES "@inspectFile /path/to/util/runav.pl" "id:159"
Example of using Lua script (placed in the same directory as the configuration file):

SecRule FILES_TMPNAMES "@inspectFile inspect.lua" "id:160"
The contents of inspect.lua:

function main(filename)
-- Do something to the file to verify it. In this example, we
-- read up to 10 characters from the beginning of the file.
local f = io.open(filename, "rb");
local d = f:read(10);
f:close();

-- Return null if there is no reason to believe there is ansything
-- wrong with the file (no match). Returning any text will be taken
-- to mean a match should be trigerred.
return null;
end
Note : Starting in version 2.9 ModSecurity will not fill the FILES_TMPNAMES variable unless SecTmpSaveUploadedFiles directive is On, or the SecUploadKeepFiles directive is set to RelevantOnly.
Note: Use @inspectFile with caution. It may not be safe to use @inspectFile with variables other than FILES_TMPNAMES. Other variables such as "FULL_REQUEST" may contains content that force your platform to fork process out of your control, making possible to an attacker to execute code using the same permissions of your web server. For other variables you may want to look at the Lua script engine. This observation was brought to our attention by "Gryzli", on our users mailing list.
Version: 2.x

Supported on libModSecurity: TBI

Reference: http://blog.spiderlabs.com/2010/10/advanced-topic-of-the-week-preventing-malicious-pdf-file-uploads.html

file upload modsecurity protection

I have installed ClamAV according to instruction

I have set the script in place.

The script is called by a new rule added via Plesk manual rules:

SecRule FILES_TMPNAMES "@inspectFile /etc/apache2/modsecurity.d/modsec_clamav.pl" \
"id:'99999932471', \
phase:2, \
t:none, \
deny, \
log, \
msg:'Infected File upload detected', \
tag:'MALICIOUS_SOFTWARE/VIRUS'"
tested syntax and restarted Apache server

could not test file upload as those were not IMAGE or PDF

Script has to get execution permissions

Why do you keep ignoring this feature request for so many years? We need proven and reliable solution that is not cost prohibitive, especially for small VPS use.
You keep increasing your licence price year on year but fail to offer added value.

It's very important.

speed up please

OPEN DISCUSSION · Jan 21, 2016 they wait for WHAT ? SIX years, ridiculous.
They seriously are listening to the community. this is a joke