I give up.

I tried left and right to try to install an email server so I could degoogle my life.

But therechnical barrier is thick and Google keeps adding more to it. Forget it. I can’t even get thru the installation process much less trying to get my shit off Google.

I figure, I don’t actually have any need for my email addresses. Just like my phone number. I never call anyone. I’m going to discourage my kids from using email at all. I’ll remind everyone I know that I don’t use email at every opportunity I get just like I remind people to not call me and that my phone number is not available.

Between spammers and Google, I just don’t need this headache in my life. My mom is much less technically savvy than the average pet. So Google will just siphon her data and when the megabits are full then you just delete the old stuff.

You don’t need it. No one will spend their life reading your emails when you’re gone or watching your videos or listening to your recordings or viewing your photos. There’s no need to worry about just deleting the pile of shit you’ve accumulated. I’m this done.

  • Shimitar@downonthestreet.eu
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    12 hours ago

    I fully agree with you: it’s NOT easy. And you must understand what you do. It’s not just deploy a container and run happy.

    I might say this is the first serious step for a selfhoster, something that goes over and beyond just hosting a service for yourself and fun, since it federates (modern term fur how email works) with the outside world.

    Are you scared of hosting email? don’t do it. You want to learn and improve your skills and you are happy with running the risks associated? go for it.

    Anyway tools like stalwart and mailcow do provide full instructions for DKIM/DMARK and DNS records that you only need to follow, so today there are easier options than the “old days”.

    Anyway you don’t have to do it on your primary email from day one, just use a test account/domain and see how it goes. Keep using your gmail account and spin it up on a secondary domain, if it works good… switch over in 6 months or 2 years as you are confortable. OTherwise, keep gmail and stop.

    • x1gma@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 hours ago

      I fully agree with you: it’s NOT easy. And you must understand what you do. It’s not just deploy a container and run happy.

      This is literally what you’ve called misinformation.

      Again, not everyone is self-hosting only for learning and experimentation only. Making a deliberate call that mailing infra might be too hard might be too hard, have too big of a knowledge gap, or is simply not worth the effort is something I’d call more serious than hardlining on “self host everything or stay on gmail”, especially in the case of mailing, where it’s pretty much impossible to self-host on your own hardware / network.

      Full instructions do not reduce any effort or resources involved or complexity of the problem. And the problem is that you’re suddenly moving from “I’m hosting a few services” to being balls deep in networking, dns, and a deceivingly easy protocol which blows up in complexity due to being federated and absolutely dominated by big providers at the same time, and all of the extensions for security.

      Except for learning, self-hosting serves a purpose. You might want privacy, you might not want to be dependent on corpo infra or external services at all, you might want to host something that offers something more or better than a SaaS solution - but first of all, it needs to work. For mail, you gain none of those. Self-hosting on your own hardware (or rather network) is pretty much impossible, so you’re reliant on a hosting provider at least. There is basically zero difference in functionality between mailing servers or providers. Sure, you’ll run into problems when copy pasting instructions, but those problems will break the service. Fucking up your DNS or networking will break your whole server. At the same time, while failing silently it will costs a magnitude of effort more than most other usually self-hosted services.