2 ms·

This is factually wrong. Your information is deprecated. Historically, yes 465 has been deprecated several years ago. But as many ISP and the largest email se

by 1996 7y ago

This is factually wrong. Your information is deprecated. Historically, yes 465 has been deprecated several years ago. But as many ISP and the largest email services kept using it, the IANA had to change its tune and 'resurrected' port 465 in this RFC. It is funny: the RFC itself describes that as a wart, but reality is a harsh mistress. Please read the outlined section 3-3 of RFC 8314 from 2018 that explain just that if you don't believe me.

teddyh 7y ago
Right; I stand corrected. Of course, this still doesn’t mean that using 465 is a good idea; ports 25 and 587 with STARTTLS (using DANE for downgrade protection) should still be preferred to using 465, which the RFC does clarify.
- 1996 7y ago
  (sorry if I insisted. A lot of people still believe 465 is deprecated. I wanted to correct that) For preference, the RFC also mentions implicit SSL is the goal. Given how far it has come, with 465 now being resurrected, I will not be surprised when in the future STARTTLS becomes deprecated - and maybe other ports besides 465. All it takes is a few large email providers to stop accepting port 587 ... and 25. Just look at how everybody has jumped into using DKIM and MTA-STS which are way more complicated and ugly, but almost required if you want your email delivered.