• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Reason for Relaylock

Superkikim

Regular Pleskian
Hi,

Some of my customers are complaining because they don't receive some emails. I have experienced the issue myself.

I have checked the logs for the sender of an email I was waiting for. I found "relaylock" issues...

I understand what relaylock is. It can be someone trying to send messages through my SMTP, or it could be a reject due to a block list.

I have checked the sender smtp email address (195.65.19.154). It is not listed in any block list.

Therefore, why do I get relaylock, when the final recipient is my own domain ??? or the customer domain...

Could it be due to multiple IP addresses set in Plesk for the same mail server ?

I mean, I have an IP for mydomain.com therefore, used also for mail.mydomain.com

and I have a different IP address for mycustomerdomains.com used for mail.mycustomerdomains.com

and the server hostname is something like "myserver.mydomain.com"...

So, is there anything considered relay, when I get messages addressed to mycustomerdomains.com ?
 
Hello,

Have you looked at the following Knowledge Base article?

[Info] Errors "database is locked" are shown in maillog. That cause them?
http://kb.odin.com/en/6172

Regards,
Denis.
 
Back
Top