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

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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.
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:
Whether SMTP access can be enabled directly on the droplet
If a support request is required, what details DigitalOcean typically expects
Any recommended alternatives (such as relay services) that align with DigitalOcean policies
Thank you in advance for your help.
Arnold Hendriks
384d3f11289345379905a243f7b817
Laveenk16
Laveenk16
e8ab71f9e5914ffba3313f6ac33bb3
1c3ae38719bc49de9abf588e704583
lincoln
76ac182105344670910aa7c62ff2a3
c3d53dcb398b418288ff41b565183d
f27857d3fd85405b8f50d9997c684d
077fced9b2084748a76237dba04166
mclaudiu