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

many "relaylock" lines in my maillog ?

F

fgilain

Guest
Hello,

i have a Plesk 8.2 server running on a linux.
in the maillog log file, i can see many many lines like theses :

Jan 25 18:29:11 mx1 relaylock: /var/qmail/bin/relaylock: mail from 84.XXX.XXX.146:13321 (gw146.societe.com)
Jan 25 18:29:11 mx1 relaylock: /var/qmail/bin/relaylock: mail from 84.XXX.XXX.146:13322 (gw146.societe.com)
Jan 25 18:29:11 mx1 relaylock: /var/qmail/bin/relaylock: mail from 84.XXX.XXX.146:13323 (gw146.societe.com)

Any idea of what it is/means ?

Thanks

Florent
 
This is normal.

Someone is trying to send to/email via your server, and failing. You'll see plenty of them.

I *think* you may see them if, for example, the IP is blocked by one of your dnsrbls, or if they are just trying to find an open relay and of course your machine isn't so they can't do anything.
 
what can i do if i found, not plenty but thousands and thousands of relaylock lines that make my server go smoking, almost literally, since i didnt knew it was running under this circumstances long time (sunday afternoon) and avg-load went to 500+, i just halted it -the rough style- and put it on again; reviewing logs i saw there were tons of different IPs from all over the world, was it an attack? or is it just normal?
 
Back
Top