communism

Do you mean to don’t write some message to root@xolat.games? 🤔

You can, but most email servers redirect mail to root@xolat.games to some other user eg xolatgames@xolat.games. The root user usually does not have their own inbox.

I’m not sure why hello is trying to write to /home/root then, that’s your problem. Do you have any Postfix aliases set up? Check /etc/postfix/aliases (there’s a chance it’s in a different location; the output of postconf alias_maps will tell you where it is).

But what’s the configs do you need? 🤔 Dovecot has about 20 separated configuration files! Do I will need to put each of them?

Just post the output of doveconf -n. Redact any sensitive info.

Just reading the first logs you pasted, it tells you the answer there. You can’t receive emails because you’re trying to receive emails as root, and writing emails to the home directory. Dovecot doesn’t run as root so it can’t write to root’s home directory.

You would ordinarily not receive mail as root. Most people set up root to redirect to your actual user. Look into Postfix aliases.

Try emailing a non-root user. It should write to the inbox. I mean, without your Dovecot configs, I can’t tell if there’s anything else wrong with them, but from the errors it seems Dovecot would work if not for the permissions errors.

Matrix works well for me.

It’s not out yet, but I’d keep an eye on Flatline. It’s by the people who make Molly (Signal client fork—it’s pretty good, been using it for years). Flatline is a Molly-compatible server implementation, i.e. so that you can host your own Signal server. Because generally if someone asked for a “reliable messenger for family use” I’d recommend Signal as a polished and reliable option, though not self-hostable unfortunately.

Same. It removes the ability to have plausible deniability of “oh I just forgot to tag it”—no, if you tagged it “non-AI” and it was actually vibe-coded, you clearly deliberately and consciously lied.

if I aggressively block each offender in my logs permanently, then the next person assigned this IP who may be a legitimate user will be unable to access my site.

temp bans exist for this reason. You can use something like fail2ban for it, or that may be overkill for your purposes, but any mechanism that blocks the IP address for a short amount of time will work. My f2b blocks spammers’ IP addresses for a day, and I don’t see repeat bans which means the spammers aren’t coming back on the same IP address, so the short ban works to stop a given spam attack.

This is just an archive. No different from using the wayback machine or any other archive of web content.

Idk about Immich but Vaultwarden is just a Cargo project no? Cargo statically links crates by default but I think can be configured to do dynamic linking too. The Rust ecosystem seems to favour static linking in general just by convention.