8 days ago
Hi Railway team,
I'm running a service (phishing-worker-dev, project wocs-server, staging environment) that needs to make outbound SMTP connections to third-party mail servers on ports 587 and 465.
Our platform is a security-awareness / phishing-simulation product. A core feature lets our customers configure their own SMTP servers (e.g. their corporate Google Workspace / Microsoft 365 relay) so simulation emails are sent from their own infrastructure and authentic sender domain. This requires the worker to open outbound TCP connections to arbitrary customer SMTP hosts.
Currently these connections fail with connection timeout - outbound SMTP appears to be firewalled. Example: connecting to smtp.gmail.com:587 from the container times out at the TCP layer (not an auth/protocol error).
Request: Please enable outbound SMTP egress (ports 587 and 465) for this service / project / account.
Details:
Project: wocs-server
Project ID: 491e0e66-a8c6-46c7-a162-46266d47e38d
Environment: staging
Region: EU West / europe-west4
Ports needed: 587 (STARTTLS), 465 (implicit TLS)
Use case: legitimate transactional/simulation email via customer-provided SMTP credentials (not bulk marketing). Authorized security-awareness testing only.
Happy to verify the account or provide any additional info. Thanks.
1 Replies
8 days ago
Outbound SMTP (ports 587 and 465) is disabled on the Hobby plan and only available on the Pro plan and above. Since your use case requires connecting to customer-provided SMTP servers, upgrading to Pro is the path forward. After upgrading, please redeploy the service for the change to take effect. More details here: Outbound Networking.
Status changed to Awaiting User Response Railway • 8 days ago
11 hours 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 11 hours ago