PLATFORM

  • Tails

    Create websites with TailwindCSS

  • Blocks

    Design blocks for your website

  • Wave

    Start building the next great SAAS

  • Pines

    Alpine & Tailwind UI Library

  • Auth

    Plug'n Play Authentication for Laravel

  • Designer comingsoon

    Create website designs with AI

  • DevBlog comingsoon

    Blog platform for developers

  • Static

    Build a simple static website

  • SaaS Adventure

    21-day program to build a SAAS

COMMUNITY
MORE
Question By

Keith Prinkey

Unsolved
Back to All Questions

Digital Ocean DNS

kaprinkey1 ・

Apr 24th, 2024 11:26 AM

Bobby,

Maybe you can better clarify for me how to get port 587 working on my droplet for SMTP server even though I use Plesk to manage the droplet and enabled port 587 for SMTP through the GUI.

I even altered the postfix.conf file and added the port and then I added it to my IPtables. The ports are still open on the firewall within digital ocean and Plesk firewall and the WAF for each domain within Plesk. DKIM and DMARC are enabled and configured and are shown in incoming emails.

I don't understand what I am doing wrong and, I have been doing this a while now plus since I knew port 25 was already blocked, I assumed they had blocked the other secure mail ports that I always use. My plan was to remove port 25 anyway via the Plesk GUI when you enable port 587. My outgoing emails are still being queued by the server while incoming is just fine.

Report
DigitalOcean Laravel News Genesis
bobbyiliev ・

Apr 24th, 2024 11:40 AM

Hey Keith!

What I could suggest here is to test out if indeed port 587 is still blocked for your account. To quickly do that you can SSH to your Droplet and run:

telnet portquiz.net 587

This will try to establish an outbound TCP connection on port 587 to the portquiz site (which is a handy site for testing connectivity on different ports).

If you get the following back:

#telnet portquiz.net 587

Trying 35.110.119.74...
Connected to portquiz.net.
Escape character is '^]'.
^]

This would mean that the port is open and the issue is not with the firewall on your server or with DigitalOcean blocking the port. If this is the case, then it would be the postfix configuration that would need to be adjusted, but I can try and spin up a Plesk server on my end and try to play around with the configuration.

Let me know if the connection works, else, if it does not and if you get a timeout after the Trying 35.110.119.74... bit, then it would indeed mean that DigitalOcean are still blocking the SMTP traffic for your account. If this is the case, you can submit a support ticket and request them to allow the SMTP traffic for your account via their support portal here:

https://cloudsupport.digitalocean.com/s/

Let me know how it goes! If the talent command works, I can look further into it by spinning up a Plesk instance on my end to see what configuration exactly might be missing.

Report