• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Clamav + Qscanq

R

RubM

Guest
Greetings,

I have a question about installing qscanq with clamav to scan the emails of my server. I have installed both following the tutorial on "http://www.hostbird.com/beta/index.php?loc=0601-0601". (Clamav was already installed on my linux box so i didn't change anything on this only the users accordingly to the tutorial.

In my opinion everything went find but when I’m testing my configuration with the command "export DEBUG=1; /var/qmail/bin/qmail-inject -a root < /usr/local/qscanq/src/TEST-BAD" i'm not getting any response literally seeing nothing. I have no idea what I did wrong.

When I’m doing a test of the clamav scanner is working with clamdscan. The response is:
/usr/local/qscanq-0.43/src/eicar_com.zip: Eicar-Test-Signature FOUND
/usr/local/qscanq-0.43/src/TEST-BAD: Eicar-Test-Signature FOUND
So the virus is recognized by clamav.

Hopefully someone can help me further because I have no idea how to find the solution to this problem.

Sincerely,


Ruben
 
I havent played around with qscanq before, but I did do rpms for qmail-scanner in the atomic repository. I suspect the integration issues would be the same between the two if you wanted to look at an alternate implementation for pointers.
 
Back
Top