On Sun, Mar 15, 2015 at 01:21:08PM -0700, Talen-J wrote:
> /To test the connectivity, try using a TELNET client to 173.194.78.26 port 25
> and see what connections happen, and if you get any rejection messages.
> That will tell you more about what is going on than
> traceroute will, in this instance./
>
> Installed telnet on my server and opened port 23 in my firewall.
DO NOT install a telnet server on your machine. Why on earth would
you do that?
Install the telnet command-line client! And use it connect to
a remote server, instead of using traceroute.
$ telnet <smtp-server> 25
> /You say your hosting provider is blocking port 25. I am puzzled that
> you're suprised when you're unable to make outbound connections to port 25.
>
> From all the how to guides on the internet I came to the conclusion that
> mail has to be received on port 25 (mandatory) but mail can sent form any
> port.
SMTP to the MX hosts of remote domains uses port 25 exclusively.
No alternatives.
> If you are saying that email has to be sent on Port 25 I have obviously
> misinterpreted the whole smtp thing and the concept of submission.
Email to remote domains MUST be sent on port 25. Email from a
null-client to a fixed smart-host relay can go over any mutually
agreed port.
The submission port (587) is common choice for MUAs and perhaps
"null-clients" (MTAs that punt all mail to a "smart-host").
--
Viktor.
