Comment on ISPs seem designed to funnel people to capitalist cloud services
conorab@lemmy.conorab.com 4 weeks agoIP blocklisting is still very much a thing as well so you can expect any mail originating from a residential IP to be rejected due to their /24 or larger having previously sent spam, and that assumes you can send server-to-server mail (destination port 25/tcp) in the first place since many ISPs and server providers block traffic destined to that port by default to prevent users from getting their IP blocklists. My home ISP blocks outbound SNMP traffic (or at least did 10 years ago) presumably to also prevent abuse. That said, things like blocking inbound port 80/tcp and 443/tcp is purely a measure to prevent people running servers at home which I’m not a fan of.
solrize@lemmy.ml 4 weeks ago
Yes, that too. I hadn’t even thought about trying to send email from a home ISP. Everyone knows you basically can’t. I thought the idea was to receive email rather than send it, so you wouldn’t be relying on some bigtech company to store it for you.
ellie@slrpnk.net 1 week ago
For what it’s worth, regarding port blocks, I had relatively good experiences with that with a local ISP here. There’s no guarantee, but many ISPs block SMTP to present accidental botnets from sending email and not technical users, so by asking might already be enough to show that you know enough about it to be unblocked.
As for the blocks, many spamlists you can get yourself unlisted. But I don’t know what permanent range blocks may exist in some systems beyond that.