Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This Exchange 2003 server sits behind a firewall with a virtual SMTP server listening on port 465 and attached an SSL certificate from Comodo to the virtual server. However, when trying to send from Apple 4.x and Outlook 2011 for Mac, it never completes the connection (time out). Oddly though, the same setup works with Thunderbird. My question is:

  • Does it matter if the friendly name of the certificate is different from the internal hostname? The machine has 2 hostnames: external and internal. The official SSL is using the external name.
  • When using a self-signed certificate with the same name as the internal, I still can't send from the and Exchange clients but I can with Thunderbird.
share|improve this question

I believe your problem lies in using a non standard port.

RFC 4409, RFC 3207, and RFC 2476 may help you.

Almost all mail routing (at least as much as I've dealt with it) is done on port 25 using TLS over standard SMTP, and the clients probably won't send on another port unless you tell it to.

There's also some info from this site:

Port 465 shows up Appendix A of the 1996 non-standard standard The SSL Protocol Version 3.0 as "Simple Mail Transfer Protocol with SSL". Unfortunately, it's not registered for SMTPs, it's registered for URD - "URL Rendesvous Directory for SSM" by Cisco. The recommended approach, at least for authentication, is to use START TLS encryption on submission port 587.

The link in the above quote is dead, but this one seems to work.

Another informative forum link here.

share|improve this answer
On the client, I specified it to use port 465 but it still didn't work. – FrancisV Jun 25 '11 at 4:16
Why aren't you using port 25? – Holocryptic Jun 25 '11 at 13:06
Security through obscurity isn't a great practice, and in this case if you chose to keep going with this route, Wireshark is your best bet in chasing down if the app is sending on the "correct" port. – Holocryptic Jun 25 '11 at 13:23

I changed the port from 465 to 587 and sending worked. I guess what happened was Apple's and Microsoft's Outlook 2011 (Mac) clients were trying to connect to port 465 but did not issue a STARTTLS command which the Exchange SMTP server required but when it was switched to 587, the clients somewhat "knew" they had to issue a STARTTLS command.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.