Report this

What is the reason for this report?

How to request or enable SMTP access on a DigitalOcean Ubuntu droplet for transactional emails

Posted on January 29, 2026

Hello Guys,

I am running an Ubuntu-based droplet on DigitalOcean and have deployed a web application called Pinggo on it.

My application requires outbound email functionality for transactional purposes only, such as:

  • User email verification

  • Password reset emails

  • Account/profile-related notifications

These emails are strictly triggered by user actions. The application does not send marketing, bulk, or unsolicited emails.

Currently, outbound SMTP ports appear to be restricted on my droplet, and I would like guidance on the correct process to enable SMTP access (for example, ports 587 or 465), or best practices recommended by DigitalOcean for handling transactional emails.

Details:

  • OS: Ubuntu (latest LTS)

  • Hosting: DigitalOcean Droplet

  • Email usage: Transactional only (verification, password reset, etc.)

  • Compliance: Will fully comply with DigitalOcean’s Acceptable Use Policy and anti-spam requirements

I would appreciate advice on:

  1. Whether SMTP access can be enabled directly on the droplet

  2. If a support request is required, what details DigitalOcean typically expects

  3. Any recommended alternatives (such as relay services) that align with DigitalOcean policies

Thank you in advance for your help.



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hey 👋

Yep, default SMTP ports like 25 are blocked by default on new accounts to prevent abuse. Even though you’re using authenticated Gmail 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 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, @sumit0ubey

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

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.