On 23 Mar 2019, at 14:03, Rupert Gallagher <r...@protonmail.com> wrote: > I disagree with Kevin on port 587, because it is vulnerable to mitm attacks.
You're going too needy too back that up with actual facts. > I was royally pissed when they introduced port 587 and deprecated port 465. > Port 587 is an RFC mandated security loophole. Port 465 is golden. Port 465 was a not-standard MSFT crutch, ut is now used for SMTPS and is fully supported. It will break some oddball multicast audio that was little used, bu that is not a problem for hardly anyone. <https://tools.ietf.org/html/rfc8314> When a TCP connection is established for the "submissions" service (default port 465), a TLS handshake begins immediately. Clients MUSTimplement the certificate validation mechanism described in [RFC7817]. Once the TLS session is established, Message Submission protocol data [RFC6409] is exchanged as TLS application data for the remainder of the TCP connection. -- Get in there you big furry oaf! I don't care what you smell!
