Hello Railway team,

I am facing an issue with outbound SMTP connectivity from my backend service running on Railway.

Summary:

The same application and SMTP credentials work correctly in my local environment.

On Railway, outbound SMTP connections are not working reliably.

SMTP test requests either time out during connection or report success from the application side without actual delivery reaching the recipient.

At this point, this appears to affect multiple SMTP providers, not just one specific provider.

What I have already validated:

The application logic is working locally.

Authentication and credentials are valid in local tests.

The backend service is healthy and deploys successfully on Railway.

Static outbound IPs were enabled and the service was redeployed.

Direct connectivity tests from the Railway console hang when attempting SMTP/TLS connections.

What I need help confirming:

Is outbound SMTP traffic restricted, filtered, or rate-limited from Railway in this environment?

Are there any platform-level limitations affecting SMTP connections on common SMTP ports such as 465 or 587?

Can you confirm whether outbound SMTP traffic is leaving my service correctly?

Is there any recommended Railway configuration for applications that need to connect to third-party SMTP servers?

Important context:

The issue does not happen in localhost.

The issue appears only in Railway.

The platform needs to support arbitrary customer SMTP providers, so I need to understand whether this is a Railway egress/connectivity limitation.