Outbound SMTP connections on port 587

Hey 👋

Yes, default SMTP ports are blocked by default on new accounts to prevent abuse. Even though you’re using authenticated SMTP, the block still applies.

https://docs.digitalocean.com/support/why-is-smtp-blocked/

Your best bet is to either:

• Reach out to DigitalOcean support and ask if they can review your account and unblock it (they don’t always do it, but worth a try)

• Or use a service like https://smtpfa.st/, SendGrid, Mailgun, or Postmark, much better for deliverability anyway. They allow SMTP over API, which is a good workaround and better for performance too.

Some SMTP providers also support alternative ports like 2525, so you might want to check if Gmail does (last I checked, it doesn’t, but maybe worth double-checking).

Let me know how it goes!

- Bobby

Heya, @jotarusso

Yes, SMTP is disabled by default on all new accounts.

First, you can request SMTP unblocking, but it’s manual. You need to open a support ticket and explain exactly what you did above: that emails are transactional only, what your app does, expected volume, and that you’ll comply with their AUP. Approval isn’t guaranteed, and even when granted, it’s usually tied to the account rather than “just working forever.”

Second (and this is what DO themselves usually recommend), use an external transactional email provider instead of running SMTP directly from the droplet. Services like SendGrid, Mailgun work well and avoid port restrictions entirely. You send mail via HTTPS APIs or authenticated SMTP relays, which DigitalOcean allows. This is the most reliable and lowest-friction option.

Third, you can relay through a mail service even if SMTP is unblocked. Running your own mail server on a droplet is technically possible, but it’s strongly discouraged for transactional email because of deliverability, IP reputation, and ongoing maintenance

Regards