On 3/25/2015 2:45 PM, Linda Walsh wrote:
James Knott wrote:
So, all you have to do is enable StartTLS and it will be used when the other end supports it too. -- I don't get the point of doing that -- especially when TLS layer seems to have some problems.
But why encrypt in sending, when most of the time it will be displayed on some mailing list which I still get, and AFAIK, isn't encrypted... If it was encrypted in all transports, *maybe* useful, but services like gmane make such encryption pointless.
StartTLS is depriated, and many big ISPs were caught stripping the StartTLS request or reply (i forget which) to force unencrypted mail so to be sent. StartTLS always starts unencrypted. Using proper ports 465,etc and encryption means the mail is either going to be encrypted or it is not going to be sent, and the men in the middle don't get to force TLS off by simply trimming a capability out of the server's reply. Linda, I think your question should be rephrased as "Why should ANY email travel unencrypted?" Give me one good reason. (I'm Not talking about PGP, GPG or any client side encryption, simply transport layer security.) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org