Hi,

Our production service is unable to send email over SMTP. We've isolated this to egress blocking on your platform, not our app or our mail provider, and would like it lifted.

Evidence:

railway logs --network --direction egress --port 587 --since 24h shows 219 outbound flows to our SMTP hosts, 100% stuck in partial state — none completed. 128 dropped with cause ICMP_CSUM, 45 with QDISC_DROP.

Connecting directly from inside the running container (railway ssh) to smtp.hostinger.com:

Port 465 (SMTPS): connection hangs, times out after 8s

Port 587 (STARTTLS submission): connection hangs, times out after 8s

Port 993 (IMAPS): connects instantly (~5ms)

So IMAP (mail retrieval) reaches the same host fine from the same container — only the SMTP submission ports are affected. This points to outbound port blocking on SMTP submission ports specifically, on your side, rather than anything with our mailbox provider, DNS, or credentials (both verified working from outside your network).

Ask: please allow outbound traffic on ports 465 and 587 for this service, or let us know if this requires a plan/verification step on our end to enable. This app sends transactional and permission-based B2B outreach email through per-client SMTP mailboxes with modest daily send caps (≈50/mailbox/day) — happy to provide more detail if useful for review.

Thanks,

Shengul