3 ms·
SMTP and IMAP are different things. Destination e-mail domains to which you want to send mail have SMTP servers. To send them mail, you have to contact their S
by kazinator 3y ago
SMTP and IMAP are different things.
Destination e-mail domains to which you want to send mail have SMTP servers. To send them mail, you have to contact their SMTP server somehow. If not directly, then through an intermediary.
> If you want something that works for everyone, it has to be port 443 and webby.
That doesn't follow. SMTP is already authenticated and SSL-protected (or can be). The port number isn't the problem, it's the spam.
Suppose that I run an alternative mail server, so that you can send me mail over HTTPS on 443.
If you're a residential subscriber, I'm still blocking you the same way.
Only, it's harder now. I have only one static IP address, and have to serve web requests on it on port 443. So I can't block you at the IP level; I have to let you access my web site (open to all) but block your use of the specific API. That's more costly in terms of system resources; I have to let you connect, and do the SSL handshake and submit requests, instead of turfing your packets at the IP layer.
> modern OS's don't let applications leave a hanging TCP connection open anymore
That has been the case since BSD Unix introduced sockets. When the application quits, the connections close. (At best, there is a graceful shutdown in the background, where the protocol stack exchanges the final FIN segments.)