3 ms·
> I also use round cube > [ their useless UX designers ruined it ] Why do you have to wait for someone to fork it? Can’t you just not update to the bad versio
by xp84 3y ago
> I also use round cube
> [ their useless UX designers ruined it ]
Why do you have to wait for someone to fork it? Can’t you just not update to the bad version? I thought that was a major appeal of hosting your own email client like this.
And given the email protocols won’t ever change, I would assume it’ll continue working the same for a decade or more.
(My only guess is a security worry, but this seems like a rather niche thing that something this niche would be unlikely to be attacked unless I were targeted by some state-level actor)
- JoshTriplett 3y agoA self-hosted personal server very much needs to be kept up to date. This isn't a "state-level actor" issue; any vulnerabilities in software like this, especially in software that someone might not update in a timely fashion, will get scanned for automatically and exploited when found. In theory, the portions that are only accessible with authentication are less security sensitive if you have only a small set of trusted users, but that's still reducing the security of your server to the security of your least security-aware user.
- xp84 3y agoHmm. I was imagining a personal server. If I were hosting a webmail client personally, I wouldn't expose it to inbound connections from the Internet at all, preferring to keep such a thing inside my LAN and via VPN only. Clearly I overassumed though, because you're right, when it could be that one would have such a thing accessible to a small team of people who don't use a VPN.
- deleted 3y ago[deleted]
- yjftsjthsd-h 3y agoYou could also just stick it behind a reverse proxy with basic HTTP Authentication; that means you have to keep Apache/nginx/caddy/whatever up to date but that part is easy and then nothing else can get to the actual application if you've done it right.