On Monday, February 23, 2015 03:35:57 PM Matus UHLAR - fantomas wrote: > On 23.02.15 14:46, Daniel Spies wrote: > >>The process configured to use msa.example.com (or more likely > >> > >> smtp.example.com to satisfy some autoconfiguration algorithms) would > >> listen on ports 587, 25, and 465 (unfortunately, there are still clients > >> that like to use this port for ssl-on-connect) > > > >On 02/23/2015 02:27 PM, Ian Eiloart wrote: > >I disabled port 465 a while ago. > > just a week or two ago I read discussion where the 465 was preferred, > because SSL is mandatory there, so there's no chance for clients to > authenticate without SSL encryption. > > ...just FYI.
SMTPS (which is what you use on port 465) is an obsolete protocol that there's no need to support unless you need to deal with old Microsoft Outlook/OE versions. SMTP+TLS on port 587 is the modern solution. You should configure your MTA not to accept unencrypted connections on port 587. Scott K _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
