• archomrade [he/him]@midwest.social
    link
    fedilink
    English
    arrow-up
    4
    ·
    8 months ago

    I edited the comment, I really meant hosting server, not domain.

    Having a custom domain isn’t a big deal, it’s really where that domain is hosted that creates forwarding issues. Since the majority of email is handled by the ‘big three’, anything that’s hosted outside of that is often flagged as spam or is refused to be delivered. That’s allegedly because there are malicious senders also hosted on third party servers (and fair enough, there likely are), but this causes a bit of a potential monopoly that could easily be abused, and there’s obvious motivation to push people into a particular service for data collection.

    Even if it doesn’t happen often, occasional failures can be a huge problem if you’re sending critical communication and it isn’t reaching target inboxes because of filtering. It’s enough of a headache that even most avid self-hosters tend to avoid it.

    • Kidplayer_666@lemm.ee
      link
      fedilink
      arrow-up
      3
      ·
      8 months ago

      That is absolutely unreasonable, as the email files don’t actually tell you who the sender is beyond the domain from where it’s sent. The email protocol is SUPER unsafe and really really easy to spoof as someone from the big three

      • archomrade [he/him]@midwest.social
        link
        fedilink
        English
        arrow-up
        3
        ·
        8 months ago

        My understanding is that it’s a combination of correctly deploying authentication (DMARC, DKIM, and SPF) and the actual IP address of the server that can get you into trouble. If you incorrectly set up authentication, OR if a malicious sender spoofs you (likely because you didn’t set up auth correctly), it can get your IP blocklisted. And unless you’re monitoring if you’re blocklisted, you often don’t know that things aren’t getting delivered until someone tells you.

        And then you’re still kind of at the whim of the big players, because they could change or update their authentication standards, and if you’re not on top of it you can find yourself in the same boat, even if you’re doing everything else right.

        It’s not impossible, it’s just a headache. But if i’m being honest, i’m a bit of a novice so it could be easier to a more trained network administrator.