Anything better?

  • HamsterRage
    link
    fedilink
    arrow-up
    4
    ·
    16 days ago

    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.

    • cmnybo@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      2
      ·
      16 days ago

      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.

    • HubertManne@moist.catsweat.com
      link
      fedilink
      arrow-up
      1
      ·
      16 days ago

      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.

    • Rikudou_Sage@lemmings.world
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      16 days ago

      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.