SMTP via port 465

We often see people trying to deliver mail on port 465, it may be technically possible that your server listening for incoming mail on port 465 but in our experience it is probably not the port you are looking for.

We pride ourselves on being able to deliver mail on any valid port where a server is listening for incoming SMTP connections.

Historically port 465 has been used for client to server communication for authenticated email sending, an ISP may request you to send mail through their servers from your email client using port 465 along with a username & password.

If you received the SMTP settings from your email hosting company in reference to sending mail, you can be certain that port 465 is not the port to supply to MX Guarddog to deliver your mail.

Servers do not communicate using passwords, so we are not able to deliver mail via port 465 in most cases.

My ISP blocks port 25, how do I get around it?

Email between servers is normally delivered on port 25, if you are trying to get around an ISP block by using port 465 you might want to try and get your email server listening on port 2525 (or some other port your ISP allows), but port 465 is probably not going to work for you.

What about encrypting my email with SSL?  I need MX Guarddog to send encrypted mail.

SSL is a deprecated communication method, servers stopped using it in the late 1990's in favor of TLS encryption which does not require any special ports.  MX Guarddog will always attempt to deliver mail over a TLS encrypted communication channel - if your server supports encryption MX Guarddog will automatically use it, there is no need to specify a special port so try port 25.