First, do a direct connection with Telnet:
telnet smtp-relay.sendinblue.com 587
Trying 94.143.17.4...
This is the basic connection troubleshooting, and works with any provider or port. Replace SendBlue and the 587 port with your actual hostname/port.
If you get this error:
telnet: Unable to connect to remote host: Connection timed out
then, the problem isn’t in Rails.
In the above example, the problem is in the port number. Services like sendinblue or mandrill (I believe gmail too) don’t support the 587 port anymore. “2525” is the new “587”.
If you get a timeout on telnet, check this:
- hostname: it’s usual to people use “smtp.sendinblue.com” instead of “stmp-relay.sendinblue.com”, “smtp.mandrill.com” instead of “smtp.mandrillapp.com”, and so on.
- port: 587 is obsolete. Major providers are now using 2525 instead. Major cloud services like DigitalOcean, block outgoing connections to 587 as well. That’s why it will work on your pc, but not on your server. I won’t even mention the “25” port, which is even more obsolete than 587. Also, some providers use specific non-default ones instead or imap.
- ipv6 vs ipv4: check if the hostname is being translated as a IPv4. If not, try to disable IPv6 (see others answers).
- hostname resolution: run the same telnet command on a machine that you know the email sending is working. Check if the translated ip (the xxx part of “Trying xxx…”) is the same. If not, go back to your server and replace the hostname with this ip. If works, change your /etc/hosts and force the hostname to use this ip.