I agree with everyone here that self-hosting email is never easy, but if you still decide to go down this route then here are two tips that I personally found very helpful, especially when you decide to host it at home:

The first is to get an SMTP relay server. That’s just another mail server that yours can log into to actually send its mail, just like an email client would. That way you don’t have to worry about your IP’s sending reputation, because everyone will only see the relay’s reputable IP.

Second is to configure a Backup MX. That’s an additional MX DNS entry with lower priority than the primary, and it points to a special mail server that accepts any mail for you and tries to deliver it to the primary server forever (or something like an entire week). So when your primary server is unreachable other sending servers will deliver mail to the backup, and it delivers the mail to the primary as soon as that’s back online.

You can get these as separate services, but some DNS providers (like Strato for example) offer both with the base domain package. It makes self-hosting an email server much simpler and more reliable in my experience.

Welcome to the Linux community. :)

You will probably never understand everything about Linux and all of its included and associated systems. That’s completely fine, no one does! That’s why we are many, and it’s what asking for advice or help is for. You can just learn whatever interests you at your own pace, and know that there will always be interesting things you haven’t seen yet.

I really like the idea of creating a decentralized network that has a fair monetization model built right in, instead of relying on donations like the Fediverse. Crypto got a very bad rep, but this kind of stuff is exactly what it’s good for imo.

It also has some core features that are missing from other similar messengers, like multi-device sync. And lastly, the devs seem pretty capable and open as well. They are very transparent with their work and seem to have the right ideas about where things should go and which trade-offs to make. E.g. their reasoning for not using the Signal protocol seems solid to me.

So I’m hopeful, but time will tell if it all works out.

Good to know I guess, but yea that’s a bit too speculative for my taste.

Looks ok to me, what in particular do you take issue with?

This UsenetServer discount link gives you 1 trial month for $1, then $50/year after that, and includes a 1TB TweakNews block and a paid PrivadoVPN account.

Completely agree! There are solutions for letting Lidarr download from Deezer and Tidal, but afaik no other music streaming services for some reason.

I’m transcoding everything to 320kbps MP3s. It’s much much smaller than flac, and I can’t hear the difference even if I try.

Fedora, I usually wait 1-2 weeks for the last bugs to be found+fixed and extensions to catch up, and then just upgrade in-place. Haven’t had a major upgrade problem for years now, it’s mostly as smooth as any other offline update. And I don’t feel like I have to reinstall the OS every few years on Linux either.

One of us One of us One of us! :)

deleted by creator

Idk when you checked, but they work pretty well now. Not quite on par with Google Docs, but the closest thing I know.

No! I prefer ______, and you are WRONG for thinking otherwise!

I can’t recommend Synology enough! They make it as easy and painless as possible to own your data again.

On Usenet altHUB and abook.link.

No, it really doesn’t. That’s like creating a bot that buys and sells company shares automatically, and saying the stock exchange has a vulnerability because your bot makes bad decisions.

I just set up a Vouch-Proxy for this yesterday. It uses the nginx auth_request directive to authenticate users with an SSO server, and then stores the token in a domain-wide cookie, so you’re logged in across all subdomains. Works pretty well so far, you don’t even notice it when you’re logged in to your SSO provider.

But you do have to tell the proxy where you want to redirect a request somehow, either by subdomain (illegal.yourdomain.com) or port (yourdomain.com:8787) or path (yourdomain.com/illegal). I’m not sure if it works with raw IPs as hosts, but you can add additional restrictions like only allowing local client IPs.

In my special case I’m using the local Synology SSO server, and I have to spin up an additional nginx server because the built-in one doesn’t support auth_request.

UsenetServer, and I used this discount link.

Can’t talk for the free tier, but my Usenet account comes bundled with a paid Privado account, and that’s working ok so far. The connections have been reliable, fast, and low latency.

My main issue has been that it doesn’t support port forwarding. Also, some GeoIP services locate many of their servers in the Netherlands, instead of where Privado says they are. Idk who’s right, but it’s definitely a problem if you want to pick a specific location.

What’s absurd is this crypto maximalist take.

You can’t just make up your own permission and punishment system, and then expect the legal system to just step aside and let it handle all disputes, especially when it comes to fraud. That’s like founding your own city in an existing country, and declaring all existing law obsolete. I know some people think this is a real possibility, but the real world doesn’t work like that.