Anton Aylward wrote:
It's not really about any _advantage_ of one port over another, it's about standards compliance.
And convention.
Right.
The whole point of things like Postfix's transport table is that it is not just port 25 for email EXCHANGE.
Which other port does your mailserver use for email exchange, Anton? (ignore uucp).
While restricting an ISP's clients so that rouges cannot get past the firewall's restriction on using port 25 either at the ISP or past it, ISPs also need to do proper certified identification and authentication *between themselves*. Hence TLS and certificates and X.509 etc etc. BY CONVENTION, poet 25 is not encrypted and so it not used for this.
Uh, I wouldn't say so. It is perfectly normal for a receiving mail server to offer or even require encryption (TLS) on port 25. Just as it is perfectly normal for a sending server to accept the offer of encryption. More and more encryption turning up for smtp. We offer optional TLS on inbound traffic. A quick check of todays logs shows more than 17000 unique clients using TLS when delivering inbound.
heads up! How many sites do you access that use HTTP rather than HTTPS?
Plenty. Still the vast majority I would say. Letsencrypt is beginning to have an impact, but still very slowly.
Would you full in a form, registration, submit password or make payment via one of the former rather than the latter?
Of course not. -- Per Jessen, Zürich (22.7°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org