• 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.

Finding a Spammer - Qmail

KrazyBob

Regular Pleskian
Somehwere on a Linux Plesk 8.2 server is a hole that is allowing spammers from all over the world to spam through. I am blocking IP's as fast as possible, but this isn't the solution. It seems that even with mail stopped from within Plesk the mail still flows. Stopping mail from SSH with

Code:
/usr/local/psa/admin/bin/mailmng --stop-qmail-send

does not stop the flow.

I have modified the sendmail file to show PHP senders and none seem to appear. All users are reported to have changed their passwords and by the looks of their passwords, they are secure and not dictionary.

The symptom is running out of SMTP connections and this is being logged in /var/log/messages as xinetd stopping for 30 seconds.

Code:
Jul 11 12:51:47 abb01 xinetd[13631]: Activating service smtp
Jul 11 12:51:48 abb01 xinetd[13631]: Deactivating service smtp due to excessive incoming connections.  Restarting in 30 seconds.
Jul 11 12:52:16 abb01 xinetd[13631]: Service smtp: server exit with 0 running servers
Jul 11 12:52:18 abb01 xinetd[13631]: Activating service smtp
Jul 11 12:52:18 abb01 xinetd[13631]: Deactivating service smtp due to excessive incoming connections.  Restarting in 30 seconds.

qmail-smtpd appears to be the sending mechanism.

The OS is CentOS 4.5 on Virtuozzo 3.0

running the PID using lsof -p <PID> doesn't reveal anything helpful.

I simply do not know where to look further.
 
Back
Top