2 months ago
Dear Railway Support Team,
I am reaching out to request assistance with outbound SMTP connectivity on my Railway deployment.
We have confirmed the following behavior:
- Connections to SMTP ports 465 and 587 are consistently timing out
- DNS resolution is functioning correctly (e.g., resolving to 142.250.27.108)
- This indicates that outbound SMTP traffic is being blocked at the firewall level
Based on this, it appears that Railway is restricting outbound connections on standard email ports (25, 465, 587), which aligns with your default policy for preventing abuse on lower-tier accounts.
Could you please assist with one of the following:
- Confirm whether my current plan allows outbound SMTP access
- If eligible, unblock ports 465 and 587 for my project/service
- Advise if upgrading to a paid plan (Developer tier or higher) is required to enable this functionality
This access is necessary for integrating with external SMTP providers (e.g., Google SMTP), which require these standard ports.
Please let me know if you need any additional details (project ID, service name, etc.) to proceed.
Thank you for your support.
Best regards,
Andrew
2 Replies
2 months ago
i have also upgraded to Pro Plan
2 months ago
Your workspace is on the Pro plan, so SMTP access on ports 25, 465, and 587 is available. You need to redeploy the service that requires SMTP for the changes to take effect. If connections are still timing out after redeploying, follow the SMTP debugging steps in our docs by SSHing into your service and testing port reachability.
Status changed to Awaiting User Response Railway • about 2 months ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago