Skip to main content

Email can be received but not send

Comments

7 comments

  • cPJustinD
    Hey there! Can you run these commands via SSH and provide me the output? curl portquiz.net:25
    traceroute -p 25 smtp.gmail.com
    This should verify that outbound connections over port 25 are working as expected. Please be sure to remove any sensitive information such as IP address from the output.
    0
  • Timile
    Hi! I've run the commands and here's the output: curl portquiz.net:25 220-hostname.hostname.com ESMTP Exim 4.94.2 #2 Tue, 14 Sep 2021 15:08:27 -0400 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail. 500 unrecognized command 500 unrecognized command 500 unrecognized command 500 Too many unrecognized commands And: traceroute to smtp.gmail.com (209.85.144.109), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * *10 * * *11 * * *12 * * *13 * * *14 * * *15 * * *16 * * *17 * * *18 * * *19 * * *20 * * *21 * * *22 * * *23 * * *24 * * *25 * * *26 * * *27 * * *28 * * *29 * * *30 * * * Waiting for your answer, thank you!
    0
  • cPJustinD
    Hello again. It appears there is some outbound restriction over port 25 occurring. Can you try disabling SMTP restrictions to see if that allows you to connect via port 25 successfully?
    0
  • Timile
    Hi, I've disabled SMTP restrictions, reboot and still cannot send email. I've retry to run the two commands and here the new results: curl portquiz.net:25 curl: (7) Failed connect to portquiz.net:25; Connection timed out And: traceroute -p 25 smtp.gmail.com traceroute to smtp.gmail.com (173.194.68.108), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 *00 * * 7 * * * 8 * * * 9 * * *10 * * *11 * * *12 * * *13 * * *14 * * *15 * * *16 * * *17 * * *18 * * *19 * * *20 * * *21 * * *22 * * *23 * * *24 * * *25 * * *26 * * *27 * * *28 * * *29 * * *30 * * *
    0
  • cPJustinD
    Thank you for that output. As the SMTP restrictions are disabled, and the outbound connections are still timing out, it appears the restriction is coming from a local or network firewall. You will need to work with your server administrator or hosting provider for further assistance in determining why the port is restricted and taking the appropriate measures to ensure that it is open for outbound requests. We've also published an article that covers this topic here:
    0
  • M_Z
    @Timile, Were you able to solve this, how did you solve it? We are facing the same problem. Would be great if you could help out.
    0
  • cPRex Jurassic Moderator
    @M_Z - the most likely explanation is that your hosting provider has blocked outbound traffic on port 25 to reduce spam.
    0

Please sign in to leave a comment.