yeah but so thats the thing. that service still is the one running your email and its likely you are going to get more issues with it being blocked just from being an little used domain. unless you run your own server and deal with the mx records and such.
In my experience, this is more a problem if you are fully running your own mail servers, not so much if you are using an established email service. My MX record reflects my email provider, and my outgoing mail goes through their servers. So I’m as trusted as they are, in general. Your mail provider should have instructions on how to set up DNS for verification.
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.
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.
yeah but so thats the thing. that service still is the one running your email and its likely you are going to get more issues with it being blocked just from being an little used domain. unless you run your own server and deal with the mx records and such.
It’s the server that matters, not the domain.
In my experience, this is more a problem if you are fully running your own mail servers, not so much if you are using an established email service. My MX record reflects my email provider, and my outgoing mail goes through their servers. So I’m as trusted as they are, in general. Your mail provider should have instructions on how to set up DNS for verification.
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.