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

qmail IP issues

K

kernelhostit

Guest
Hi guys,

Since upgrading plesk to 8.6.0 i've noticed that qmail has stopped logging the source ip address of connections. I'm not sure what has happened but relaylock always logs '0.0.0.0'. For example:

relaylock: /var/qmail/bin/relaylock: mail from 0.0.0.0:4493 (not defined)

There's not one single entry showing a correct source IP. All ip's logged by qmail are 0.0.0.0.

POP3/apache etc are all showing correct source IP addresses.

Any ideas people?

Thanks in advance
 
You must log in or register to reply here.

Similar threads

wasiwarez
Issue Issues with Plesk/bind configuring as master and slave nameserver
Replies
7
Views
5K
wasiwarez
wasiwarez
I
Resolved Preventing bot brute force probes against Postfix/SMTP
Replies
5
Views
4K
iainh
I
H
Issue Cloudflare - Logs showing Cloudflare IPs, not client IP
Replies
15
Views
7K
Sebahat.hadzhi
Sebahat.hadzhi
I
Forwarded to devs Postfix fail2ban filter misses authentication failures
Replies
1
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
Hangover2
Question Handling Large DDoS Attacks (Many Rotating IPs)
Replies
9
Views
5K
cmaurand
C
Back
Top