ios VS Mailcow

Although I don't need to dial a VPN before accessing my NAS outside, but expose NextCloud on public network is not safe. There are already some people request NextCloud add support for client-side certificate authentication on their app, I am also very interested in this feature, it will improve the security of public network access.

I recently setup my first unraid homelab and ended up going with a cloudflare tunnel + warp setup for accessing docker/VMs like Nextcloud remotely. Everything seems to be working well through the browser, but the nextcloud desktop and mobile apps give me "unknown" errors when I try to connect. I've seen a few other posts and issues submitted on github in regards to this (https://github.com/nextcloud/ios/issues/1565), but I haven't seen anyone mention a work around besides creating another connection workflow (ie. separate VPN). Any suggestions?

With multiple android phones come and go in the past 8 years or so, the background upload seems to stand its ground.

The real problem here is iOS and its lack of proper background tasks. See: https://github.com/nextcloud/ios/issues/215 -- they tried every possible way to persuade iOS into running background sync, but still hit and miss.

I have to request access to my wife's iPhone and manually trigger some :)

One small suggestion here -- PhotoPrism went with `tensorflow.js` to load up classification models, and I recommend a "real" TF or PyTorch installation to properly leverage the computation resources. The difference is huge even running cpu-only because it's wasm vs. proper BLAS library.

I worked on a nodejs binding for native ONNX runtime (not publicly) so that's also a possible way out.

I've been running mailcow [1] on a Hetzner cloud server for a few years and am pretty happy with it.

[1] https://mailcow.email

I have been searching for a self-hosted suite similar to Google Worksuite. I found the following: 1. Mailcow - https://mailcow.email/

Yes, I switched to mailcow (https://mailcow.email) and installed Roundcube via the excellent tutorial (https://docs.mailcow.email/third_party/roundcube/third_party-roundcube).

I've heard good things about mailcow

https://mailcow.email/

You can self host email if you really want to, but it's really more trouble than it's worth. If you do self host, you have to worry about the consequences of missed emails if your server or Internet ever goes down, and you'll have to use someone else's SMTP server if you don't want your emails to go directly to spam. The cheapest good SMTP server is Amazon SES, which I believe is $0.10 per 10k emails. I've been looking into mailcow for self hosting an email server and it seems the best way to go.

However, https://mailcow.email/ is the ONLY exclusion I make for that. As it's an all in one docker managed solution. Where the only things you have to worry about is the reputation of your mailing IP.

But its probably easier to use a dockerized container with all the mail stuff integrated and pre-setup like: https://mailcow.email/

If you're looking for a full solution that I haven't tried (due to resources) try: MailCow. Good luck.