• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Can't connect to SMTP despite correct firewall rules

Constantin Kraft

New Pleskian
Hello fellow community!

I run SuiteCRM which needs to connect via SMTP to a mail server which I resides on the same host.

Despite having opened ports 587 and 465 for ingoing and outgoing traffic I can't `telnet example.com {587,465}` … it produces `Connection refused` (executed in shell on the same host).

However from outside I can connect to the mail server via Thunderbird.
Also netstat confirms the ports are opened for incoming traffic.

Can someone help/give a hint?
It would be much appreciated.

Thanks in advance & best regards,
Constantin
 
Maybe the problem with incorrect hostname resolving on your server? Checking iptables rules also would be useful.
 
It was a firewall issue, which could be solved by disabling the catch-all rule which prevents outgoing traffic.

When activated it somehow overrides the rule that explicitly allows outgoing traffic on ports 465 and 587.
The corresponding lines in the screenshot are the third and fifth (catch-all rule now configured to allow) from below.

Any hints on what's wrong?
 

Attachments

  • Screenshot-2018-1-26 COINS Plesk.png
    Screenshot-2018-1-26 COINS Plesk.png
    137.9 KB · Views: 12
Last edited:
It was a firewall issue, which could be solved by disabling the catch-all rule which prevents outgoing traffic.

When activated it somehow overrides the rule that explicitly allows outgoing traffic on ports 465 and 587.
The corresponding lines in the screenshot are the third and fifth (catch-all rule now configured to allow) from below.

Any hints on what's wrong?
AFAIK there is, by default, no outgoing block....

On the other hand... I manually manage my firewall.

Even if you have some tool or gui to manage your firewall one should really try to understand how iptables works.
If you knew you would have had no need to ask this question.
 
Back
Top