If you upgraded to the pro plan recently, you need to redeploy your service. Restarting won't work.

Yeah, I have done that and did not help (I didn't word it correctly)

Well, then there is one thing left to check:

Yes, I really read the documentation before asking the question. I use AWS SES, I could not reach out to a human but according to their AI support, they arent blocking anyone.

Maybe the changes haven't taken effect yet. Try to wait some time, and redeploy again. It might work.

I am done with that as well.

Is there any update on this, having similar issues, need to send emails via SMTP and SES. normal transactional emails, "verify account" "reset password"

I would narrow this down into two separate checks: SES-supported ports vs. Railway/provider blocking.

Your test includes 2525, but Amazon SES does not list 2525 as a supported SMTP port. For SES, the useful ports to test are:

- 587 or 2587 for STARTTLS

- 465 or 2465 for TLS wrapper / SMTPS

- 25 only if you specifically want port 25, which is commonly restricted

So from the Railway shell I would rerun the check with the SES alternate ports:

```bash

H="email-smtp.eu-west-1.amazonaws.com"

for P in 25 465 587 2465 2587; do

(timeout 5 bash -c "</dev/tcp/$H/$P" 2>/dev/null && echo "PORT $P: OPEN") || echo "PORT $P: CLOSED"

done

```

Railway's outbound networking docs say SMTP is available only on Pro and above, and the service must be redeployed after upgrading. You already did that, so if 465, 587, 2465, and 2587 are all closed from inside the Railway container, this is no longer a listmonk config problem. It is a network/provider reachability problem between Railway's outbound IPs and SES.

If at least one SES port opens, configure listmonk to match the port mode:

- 587 or 2587: STARTTLS

- 465 or 2465: TLS/SSL wrapper

If all SES SMTP ports stay closed, I would stop trying SMTP for this deployment and use SES over HTTPS instead. AWS SES API v2 supports SendEmail over HTTPS at POST /v2/email/outbound-emails, which avoids SMTP ports entirely. Since listmonk's built-in email backend is SMTP, the practical listmonk path is either:

1. switch to an email provider with an HTTPS API that listmonk can use through a messenger/bridge, or

2. add a small listmonk HTTP messenger service that receives listmonk campaign JSON and calls AWS SES SendEmail / SendRawEmail with the AWS SDK.

That keeps SES, avoids blocked SMTP ports, and matches Railway's own recommendation to prefer HTTPS transactional email APIs when SMTP connectivity is unreliable.