Ahh gotcha, makes sense.

Got it, thanks.

When you switched, did you lose all of your Gitea data? Or was that somehow importable?

Out of curiosity, how did you switch to Forgejo? I thought Gitea and Forgejo have diverged to the point where you can no longer just switch over without losing stuff.

It makes a certain amount of sense. More deduplication means more CPU (and IO) spent on that work.

The only disadvantage I find is that there is no cross system deduplication.

You could achieve this by having all machines write to a single Borg repository, where everything would get deduplicated. But downsides include: 1. You lose everything if something goes wrong with that one repo, and 2. You’d have to schedule backups across all systems so as not to run at the same time, because the single repo can only have a single writer at once.

Also protecting you from the East Wing of the White House.

Same! Okay, not without problems, because running a mailserver isn’t maintenance-free. But Mailu has been generally solid and it works with Docker. (And Podman, unofficially.)

I went down this very same twisty road a while back with rootless Podman. I tried several of the solutions you mentioned. None of them worked. The actual working solution I finally settled on was using Proxy Protocol to pass the original client IP from the host into a container. In my particular case, I’m running a very basic HAProxy config on the host that’s talking Proxy Protocol to Traefik running in a container. And it works great; actual client IPs show up in the logs as expected.

In your particular case, you could probably run HAProxy on the host and have that talk Proxy Protocol to Caddy running in a container.

You can do calendar and contacts separate from email. Try Radicale. I’ve been using it for years.

Another container-based alternative in that space is Mailu.