8 days ago
Hi,
We're running a production application on Railway (project: spectacular-light, service: commaxel, environment: production) that needs to send transactional/business email via authenticated SMTP to our customers' own mail servers.
Outbound SMTP connections are currently failing with [Errno 110] Connection timed out. We've confirmed this is not a configuration issue on our side: the same credentials and settings (host, port 465, SSL/TLS) work correctly from other environments. The connection simply times out when initiated from the Railway container, which indicates outbound SMTP is blocked at the network level.
We are connecting to external mail servers (e.g. mail.example.com:465, SSL/implicit TLS) using per-tenant credentials — we are not sending bulk or marketing email, and we are not running our own mail server. Each message goes out authenticated through the customer's own mailbox.
Could you please:
Confirm whether outbound SMTP (port 465, and 587) is blocked by default on our plan, and
Enable outbound SMTP for our production service, or advise the supported path to send authenticated SMTP from Railway.
Happy to provide any additional details. Thanks for your help.
Alberto
1 Replies
8 days ago
Outbound SMTP is only available on the Pro plan and above, while Free, Trial, and Hobby plans have SMTP disabled.
For sending emails from your application, please use a dedicated email service that provides HTTPS APIs. More information can be found in our documentation: Outbound Networking
Status changed to Awaiting User Response Railway • 8 days ago
Status changed to Solved euroteamintadv • 8 days ago