inlets VS AnonAddy

Thanks for the guide. Just to mention another option is https://github.com/inlets/inlets-operator

adding on to this, if OP goes down the local k8s cluster route for learning purposes, they can then hook it up to a public load balancer with this TCP tunnel thingy called inlets for a few bucks a month https://github.com/inlets/inlets-operator

Thanks! To be honest, I was thinking of a tutorial too. But then I stumbled upon the inlets-operator (the one from the visualization in the article) and its code actually looks very good in my opinion. It's concise, straightforward, and seems to be idiomatic. I do recommend taking a look at it.

With providers like Addy and SimpleLogin it is possible to use your own domain.

> https://addy.io/

This is one of a few reasons I have started to use email forwarders such as AnonAddy.

https://github.com/anonaddy/anonaddy

Not all of my emails have been moved over yet, but over time I plan on depreciating almost if not all of my main emails from logins.

For receive-only e-mails, take a look at addy.io as a free alternative to DDG. It's easier to manage with an account page listing every alias you create, with the option to block if required.

I use https://anonaddy.com/

My only complaint: 90% of the emails coming from AnonAddy, which is the alias service I use for all of my accounts, end up in the spam folder.

AnonAddy - https://github.com/anonaddy/anonaddy/blob/master/SELF-HOSTING.md OR SimpleLogin.io The real issue you are going to face is being able to receive emails on your server. If you are trying to do this at home, most home ISPs block incoming port 25. Even on most cloud providers you will face the same problem.

Anonaddy, basically the exact same product made by different people, can also be selfhosted. https://anonaddy.com/