I use posteo.

If you’re thinking of using your own domain, I would suggest using forwardemail.net

They weren’t.

Google runs it’s own scans against domains.

Yes.

I made the mistake of naming my emby instance https://emby.example.com

On emby, if you don’t have a session cookie, it opens on an authentication page.

I’ve had Google label it as a mitm attack and get labeled malware three times. It gets fixed in a day or two upon review, but all major browsers block it during that time.

It’s amazing how many of those started with Lennart, too.

I’ve been self-hosting a bunch of stuff for over a decade now, and have not had that issue.

Except for a matrix server with open registration for a community that others not in the community started to use.

We’ll see if your reading comprehension liabilities extend to self-hosting.

Seafile is extremely easy to set up and does one thing and one thing well.

It does store your data as binaries, so it would be a bit harder to restore than Nextcloud due to that, but I’ve never had an issue with seafile.

Of course, I didn’t have a problem with Nextcloud until an upgrade borked the installation bad enough that even restoring from backup couldn’t solve the issue.

ZZ

Or ‘ZZ’