SMTP 530 error: “denied access” While Accessing MailEnable

June 19, 2013 / General Discussion

The tutorial provides a solution for the SMTP 530 error: “denied access” occurred on the parallel Plesk panel for windows while accessing the MailEnable. The tutorial applies only to the following Plesk panel versions for windows dedicated servers.

  • Parallels Plesk Panel 11.x for Windows
  • Parallels Plesk Panel 10.x for Windows
  • Parallels Plesk Panel 9.x for Windows
  • Parallels Plesk Panel 8.x for Windows

Usually, when accessing the MailEnable the SMTP service shows an SMTP 530 error: “access denied”. It simply means that the connection has been denied access in the SMTP. Access Control properties of the MailEnable Administration Program on the server or the IP blocked. Due to many subsequent invalid commands.

530 ESMTP MailEnable Service, Version:0–1.1 denied access at 19/06/13 17:04:25

Connection to host lost.

To solve the SMTP 530 error: “access denied” error, follow the steps shown below:

Using the administration console, go to the following location:


Now, simply right-click on “SMTP” and select “Properties” in the menu.

Now move to the “Inbound” tab and click on the “Access control”.

Here, make sure you have set the Access control option to “Granted access” and the incoming connection IP is not listed under the “Except those listed below” window.

Basically, if the SMTP security “connection dropping” option is enabled. The incoming IP address automatically added to the inbound “Access control” list. If not enabled, the SMTP service will drop and add the connecting IP address to the inbound “Access control” list. When the failed SMTP service will drop the connection when it notices many subsequent invalid commands.