matt

Nice! I updated my instance already. Thank you to all contributors! 🥳

There could be any number of reasons. For one, you can avoid power-tripping mods that ban people they disagree with just because they can. Even though they chose the same name, different communities might have different purposes or rules. Just find the ones you like and subscribe without worrying too much. Everything is federated so it doesn't matter.

Since nobody bothers to check previous posts (even from just a day or two ago), I won't bother with the details. All I will say is to learn the purposes of an MX record and how sending email works (and the differences). Hint: MX records have nothing to do with sending emails from your server. Just use a third party SMTP service in your config.hjson file.

I agree with @terribleplan@lemmy.nrd.li that the inclusion of a postfix SMTP container and using that in the example configs is probably doing more harm than good.

You shouldn't need the Postfix container at all unless you want to manually set that up and know what you're doing. You configure your SMTP settings in the config.hjson file as outlined in the example defaults.hjson file. I'm using a third-party SMTP provider to avoid any deliverability issues with sending emails directly from my server's IP address. Just ensure you configured your DNS correctly (DKIM, etc.), punch in the info, and it should work.

For Lemmy users specifically, I believe Lemmings has been widely accepted. However, when referring to a user of federated software in general (remember they can potentially communicate with other federated software), we could refer to each other as "Fedizens" of the "Fediverse". I have seen a developer use the term "Fedizen" in one of their code examples, and I like it as a more inclusive name.

I ran email server with Mailcow Docker. Easiest way I have found. It is perfect to host your own mailbox but as other have said, the sending from your IP might just get blocked by other big mail servers. Luckily Mailcow allows you to use it as a SMTP relay and you can route outbound mail through the well known SMTP services.

I have had an issue with updates to Nginx Proxy Manager breaking itself in the past so I switched to Traefik.

NPM is much more user-friendly when it works. However, as mentioned, Traefik integrates directly with docker through labels, making it very convenient if not a bit more of a learning curve.

So far, the only annoyance I have with Traefik is that I haven't found a very easy way to host itself on a separate server from where the containers are running because it uses the docker.sock file to pick up the labels on running containers automatically. Instead, I manually create files for the files provider. I don't think this is an issue if you are using Kubernetes, but I haven't gotten all the way down that road quite yet, as it is a bit overkill for me.