5 ms·
You're thinking of end clients. This is server to server communication and Fastmail supports STARTTLS of course. $ dig mx fastmail.com +short 10 in1-sm
by spindritf 12y ago
You're thinking of end clients. This is server to server communication and Fastmail supports STARTTLS of course.
$ dig mx fastmail.com +short
10 in1-smtp.messagingengine.com.
20 in2-smtp.messagingengine.com.
$ telnet in2-smtp.messagingengine.com. 25
Trying 82.221.106.241...
Connected to in2-smtp.messagingengine.com.
Escape character is '^]'.
220 tlxc1.messagingengine.com ESMTP . No UCE permitted.
ehlo my.hostname
250-tlxc1.messagingengine.com
250-PIPELINING
250-SIZE 73000000
250-STARTTLS
250-ENHANCEDSTATUSCODES
250 8BITMIME
- kijin 12y agoThe article is about end clients on residential and/or business lines. There is no reason for client-to-server communication to rely on STARTTLS on port 25.
- zurn 12y agoThere's also no reason to discount server-to-server SMTP on residential or business lines. Especially since this is part of the larger net neutrality discussion.
- feld 12y agoI worked at an ISP and no, net neutrality aside, SMTP on residential is bad bad bad. It should be permitted only at the customer's request, but probably won't fix the fact that their subnet is on a global spam blacklist.
- zurn 12y agoThe point of NN is that the ISP shouldn't get to make that decision. Even "allow on request" is very problematic because it's a slippery slope. Many people run SMTP at home mostly to receive mail, because the ISP is legally obligated to retain mail logs for law enforcement etc. (EU data retention law)