21 minutes ago
Hi Railway Support team,
I run a small stateless Node.js mail bridge on my Railway account for my wedding planning software (Definitely Yes Suite). The service allows individual planners to connect their own authenticated business mailboxes (e.g. via TransIP / Dutch domain providers) over secure IMAP (port 993) and SMTP (ports 465 and 587).
Currently, outbound SMTP connections to smtp.transip.email on ports 465 and 587 time out due to the default outbound email port block.
Could you please unblock outbound ports 465 and 587 for this project/service?
Key details about our use case:
Nature of traffic: Strictly 1-to-1 interactive business correspondence initiated by authenticated users.
No bulk/marketing mail: We do not send marketing campaigns, newsletters, or bulk email through this service.
Authentication: All outbound connections authenticate against the user's legitimate mail provider (e.g. TransIP) using their personal credentials.
Destination servers: Standard commercial European mail providers (primarily smtp.transip.email).
Please let me know if you need any additional project IDs or verification details from my end.
Thank you for your help!
Kind regards,
Mariska van der Meer
Definitely Yes Suite
1 Replies
20 minutes ago
Outbound SMTP (including ports 465 and 587) is only available on the Pro plan and above, and your workspace is currently on Hobby, where SMTP is disabled. This applies per plan, so we can't open these ports for an individual project or service.
To use SMTP for your mail bridge, the workspace would need to be on Pro, and after upgrading you'd redeploy the service for the change to take effect. On Hobby, outbound email needs to go through a transactional email service that uses an HTTPS API instead. More details are in our outbound networking docs.
Status changed to Awaiting User Response Railway • 20 minutes ago