Vultr blocks outbound port 25 on new instances to stop spam; use 465 or 587, or request an unblock.
By default, outbound traffic on port 25 is blocked on all new Vultr Compute Instances. This helps prevent abuse such as spam and protects the IP reputation of Vultr's infrastructure.
Port 25 is commonly used for unauthenticated or relay SMTP traffic, which is frequently exploited by spammers. To maintain a secure and trustworthy environment, Vultr blocks outbound traffic on this port by default.
Yes. You can still send email using ports 465 (SMTPS) and 587 (submission) through an external SMTP provider like:
These providers support secure, authenticated mail delivery and are recommended over running your own mail server.
If you have a legitimate need to send mail over port 25 (e.g., legacy software that doesn’t support ports 465 or 587), you can submit a Support Ticket to request unblocking. Provide details about:
Approval is reviewed case-by-case and not guaranteed.
Vultr recommends using authenticated mail relay services instead of hosting your own mail server. Running a self-hosted mail system requires ongoing monitoring, security hardening, and careful management of deliverability.
0 Comments
Be the first to comment and share your perspective with the community.