If you need unblocked ports you can also use <a href="https://hoppy.network" rel="nofollow">https://hoppy.network</a><p>We provide ports 25, 465, 587<p>Disclaimer: cofounder of hoppy
This makes alot of business sense, most orgs know better than to homebrew their mail env on (lets be honest here) "basement hosting LLC". So that leaves the people that are spamming/phishing as the core SMTP customer here.<p>We lost the personal self hosting fight long ago. I used to do it, but now i pay protonmail to do it for me and even that is losing its luster since proton technology IP blocks are pretty radioactive at this point. Some day will have join the outlook or gmail gang which makes me sad; but setting here in my chair staring at my orgs email firewalls and seeing 80+% inbound volume being auto-blocked as spam, bulk or phishing it make me wonder if anything of value was lost.
Most of the VPS providers have been implementing variations of this for a few years now. Most of them will not block ports on accounts created before a certain date and will open the ports for people that open a ticket and state they will not be sending UCE and are responsible postmasters that will secure their mail servers inbound traffic and accepting an agreement that if they abuse it or let someone else abuse it their account is gone. Seems more than fair to me. It's a nice alternative to having to say, <i>"and this is why we can't have nice things."</i> We can have nice things.
"we strongly recommend against running your own mail server in favor of using a dedicated email deliverability platform"<p>This is ridiculous. We have collectively surrendered email and became hostages. I'm as guilty as everyone* and don't really see the solution.<p>* most. You're the brave ones.
It looks like this is only for accounts created after June 22, 2022. Mine are older and their emails have been going out before and since.<p>I never even heard about this.<p><a href="https://www.digitalocean.com/blog/smtp-restricted-by-default" rel="nofollow">https://www.digitalocean.com/blog/smtp-restricted-by-default</a>
Old support page: <a href="https://web.archive.org/web/20241217094107/https://docs.digitalocean.com/support/why-is-smtp-blocked/" rel="nofollow">https://web.archive.org/web/20241217094107/https://docs.digi...</a><p>Not sure how this change makes sense.