3 hours ago
root@b54a54f66c2f:/app# SMTP_HOST="smtp-relay.brevo.com" bash -c '
for port in 25 465 587 2525; do
timeout 1 bash -c "</dev/tcp/$SMTP_HOST/$port" 2>/dev/null && \
echo "$SMTP_HOST port $port reachable" || \
echo "$SMTP_HOST port $port unreachable"
done
'
smtp-relay.brevo.com port 25 unreachable
smtp-relay.brevo.com port 465 reachable
smtp-relay.brevo.com port 587 reachable
smtp-relay.brevo.com port 2525 reachable
Pinned Solution
2 hours ago
you can try switching to a different reachable port again and redeploy it, sometimes smtp services block the ports and have a preferred port as well. try 2525 if u did not previously
6 Replies
3 hours ago
Port 25 is blocked on our infrastructure to prevent spam abuse. Your test shows ports 465, 587, and 2525 are all reachable, so you can use any of those with Brevo. Port 587 (STARTTLS) is the standard recommended port for authenticated SMTP submission.
Status changed to Awaiting User Response Railway • about 3 hours ago
3 hours ago
i am using 587 and 465 still same issue, Details: host=smtp-relay.brevo.com port=485 user=a017bd001@smtp-brevo.comfrom=admin@mindmesh.market
Status changed to Awaiting Railway Response Railway • about 3 hours ago
Status changed to Open Railway • about 3 hours ago
3 hours ago
Have you redeployed your services after upgrading to Pro?
There's also a "debugging smtp issues" section on the docs which is worth taking a look.
medim
Have you redeployed your services after upgrading to Pro?There's also a "debugging smtp issues" section on the docs which is worth taking a look.
2 hours ago
yes i have redeployed it, and the logs in initial comment are the debuggg logs
2 hours ago
you can try switching to a different reachable port again and redeploy it, sometimes smtp services block the ports and have a preferred port as well. try 2525 if u did not previously
magic0ven
you can try switching to a different reachable port again and redeploy it, sometimes smtp services block the ports and have a preferred port as well. try 2525 if u did not previously
2 hours ago
thanks it worked on 587, weirdly i deployed initially on the 587 only
Status changed to Solved medim • about 2 hours ago