this post was submitted on 07 Feb 2025
188 points (95.6% liked)
Open Source
33551 readers
73 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's a little confused. From what I remember, it's the server that matters, not the domain when being blocked. If you self-host this is a problem, but not if you use your own domain on a commercial service.
The "MX records and such" are all a function of domain management. You'll have to do this whether or not you self-host.
Some TLDs that are well known for spam get blocked. If you stick with a .com, you will usually be fine if you are using a decent mail server.
I mean at least initially with things like nightmare host (im making a joke im not sure if dreamhost is still around) you did not need to mess with the mx records if you just went with their built in. We definately had some issues with email getting marked spam or blocked but admitadely that could have been from the services source servers having to much spam coming from it.
It's actually both, server IP and domain, separately, both have their own reputation and if either is deemed spammy, your mails will be sent to spam.
Source: Am an architect and a dev for a newsletter provider, we deal with reputation issues multiple times a month. Usually because one of our clients, who definitely never bought any database of contacts from a shady origin, hit a spam trap which immediately sends your reputation to red numbers.