Relay mail : Connection timed out

Hello everyone,

SMTP-In is ok but having issues with the outbound emails.

Could anyone help with the logs below :

SMTP-OUT:0000012C: Relay mail 394C01: unable to connect to 185.70.41.101:25: Connection timed out
SMTP-OUT:0000012C: Use 185.70.40.102 to relay mail 394C01 for domain protonmail.com
SMTP-OUT:0000012D: Relay mail 394C01: connecting to 185.70.40.102:25
SMTP-OUT:0000012D: Relay mail 394C01: unable to connect to 185.70.40.102:25: Connection timed out

Another example

SMTP-OUT:0000012E: Relay mail 118342: connecting to 217.70.178.1:25
SMTP-OUT:0000012E: Relay mail 118342: unable to connect to 217.70.178.1:25: Connection timed out

Any suggestions?

Cheers

Hi
It’s because your connection to destination server on port 25 is banned.
For test you can run telnet on server:

telnet 185.70.40.102 25

What returns above command?
Share it.
Good luck

Hi Mohammad,

How can I push smtp-out to use port 587?

Cheers

Axigen sends emails to port 25 by default unless you define specific ip and port for specific domain.
@indreias can answer that.

Hello Daniel,

First of all Mohammad point you in the right direction: it seems that your system is located in a place where external TCP connections to “external world” port 25 are blocked.

  • In case your system is installed in AWS - than you have to open a ticket to them, requesting to lift this action as a permanent exception.
  • In case your system is installed in GCP - than you have no luck as, from my knowledge, they are not allowing any exceptions to this action
  • In case your system is in a place where somebody else control the router (like your ISP) you may ask them to lift the action

And so on.

Now, your suggestion to use another port (587 instead of 25) will not work as the default port for submitting email messages is port 25. Port 587 (and 465) should be used by mail clients when submitting authenticated messages (usually to external domains).

On the other side, if you receive from your ISP or cloud provider, an SMTP gateway that could act as a intermediary smart relay, than you may configure it (IP address and port) via WebAdmin.

HTH,
Ioan

Thank you both. I wasn’t aware that Azure is blocking emails sent directly using TCP port 25.

Cheers,

Daniel