3 ms·
https://xkcd.com/927/ https://xkcd.com/927/ The problem isn't the port. The problem is the behaviour. HTTP itself is on its way out, you should be recommendi
by dredmorbius 4y ago
https://xkcd.com/927/ https://xkcd.com/927/
The problem isn't the port. The problem is the behaviour.
HTTP itself is on its way out, you should be recommending HTTPS if you're going to go this route.
Increasingly, I find HTTP(S) requests are blocked by various mechanisms, typically CAPTCHAs or similar.
And the problem ultimately with email isn't the network requests, by and large, it's the spam. Reimplement some universally-accessible messaging protocol over another port or service and you'll simply find you've kicked the can and inherited the old problems.
I'm not saying SMTP is faultless (for a rather tongue-in-cheek take, see <https://news.ycombinator.com/item?id=32587346 https://news.ycombinator.com/item?id=32587346> and responses within that subthread and elsewhere on the post, particularly <https://news.ycombinator.com/item?id=32591880 https://news.ycombinator.com/item?id=32591880>). But you'll have to do more than just swap port numbers to fix it.