For inbound, I use Postfix + rspamd + dovecot directly to my server. Outbound, I used to send it directly from my server. I did this 15+ years with DKIM, DMARC, and SPF. It worked well for like 95% of the emails I sent, but I started relaying through smtp2go.com after I had just a couple really important emails not get delivered or me not be sure if the recipient saw them.
What I’m worried about is whether we’ll be able to connect to anything else. With open source, sure you can remove age gates, but with device attestation coming to a device near you, you won’t be he able to log into your favorite game or website.
Its already like that with CloudFlare randomly blocking my Firefox on Linux install occasionally.
Yeah it’s useful and I’ve been using it for my home lab, but too many of my containers want outbound connections to the Internet. Like Forgejo needs :443 to be able to mirror or remote push repositories, so either I have to identify and allow list github.com, gitlab.com, etc. or end up allowing 0.0.0.0/0:443 which is not very strong protection.
I’d love for some kind of CNI or network plugin that filtered based on domain name.
Since you’re using Kubernetes, have you looked at external-dns? In my home lab, I use external-dns to take Ingress and Service resources and register them into my internal DNS zone. I use the etcd backend. external-dns registers zones in etcd, then CoreDNS queries from etcd. As soon as I create a new Ingress, it’s automatically registered and pointing to my Traefik service.
https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/coredns-etcd.md
Why is a lake name stored in code versus a database?
Just take a picture of it and I’m sure muse will figure it out for you. I’m sure somebody will do it, but I can set a calendar reminder myself.