What's coming in 5.6
Yeah, I would love to get the autoconfig functional in this release. I haven't gotten to that yet, and will probably need help of everyone to test auto-detection in variety of clients.
Mallewax last edited by
@girish Love it....:-) Thank you for your consideration!
Mallewax last edited by
@girish Maybe this is of help, too....
We now have server side signatures as well. These can be set per-domain:
I have also made some good progress with NC and WP optimizations. I will make a separate post for that.
@doodlemania2 It turns out collecting network information for each container is quite complicated. It's easy to collect the stats at a point in time (like docker stats does) but to do it over a time period, requires us to periodically track the container/process. I put some notes here - https://git.cloudron.io/cloudron/box/-/issues/734 . I have to postpone that task since it's quite complicated. If someone has better technical knowledge on this, please do leave a note on gitlab.
Thanks for the update good sir!
Any ETA on 5.6? Can't wait for these mail improvements.
@d19dotca It's getting here, a couple of things left. Hopefully late next week
For the email auto-configuration, for now I will just add docs on how to set this up manually. It's a bit complicated to automatically set all this up because outlooks requires SRV records (for which we have to write automation code for the DNS providers) and thunderbird/k9 requires setup of
.well-knownfiles. This has the same issue as mastodon where we can automate only the website is also on Cloudron. So, for now, I will put docs on how anyone can set this up manually.
@girish Can Cloudron not write to the "well-known" folder on the host?
I was thinking matrix could be a switch in the admin panel.
@girish I would guess that most people have everything they can on cloudron, is that the reality in the field?
marcusquinn last edited by
- One Cloudron managed server has Email hosted with it's various subdomains
- Another (maybe Cloudron managed) server has the root website domain.
- So the
.well-knownfile needs hosting on the root domain server.
I've been thinking a fair amount recently about whether to
www.the main website or not.
Originally, I though, who still types
But, that misses the ability to manage it as just another subdomain, and have the main root domain 301 redirect to
Reasons for having
www.? Well, this use-case could be one. CNAME load-balancing could be another.
I'm thinking that Google does
www.for their main domain and many other big players do too, so maybe they are right and my non-
www.thinking for succinct brevity was missing some of these other possibilities that using
Might be an SEO risk changing large websites and potentially messing up the 301 redirects for all indexed URLs but I'm having a serious think about going back to
www.given those using it probably know more than I do as to why it might be better.
d19dotca last edited by d19dotca
@marcusquinn For most people it doesn't matter if we use www or non-www, but I found this page many years ago which has made me stay consistent in using www over non-www, which you may find interesting too.
It mostly comes down to technicalities really (but this is probably a good example of one too): https://www.yes-www.org/
Or more specifically, this direct page for the reasons why to use www over non-www: https://www.yes-www.org/why-use-www/
With that said though, while the vast majority of major websites use www, some very large companies don't either, so there must be some valid reason or workaround they've found to any restrictions. Twitter is one that comes to mind, for example. That article actually mentions Twitter too. haha.
marcusquinn last edited by
@d19dotca Very handy, thank you - you and they have me convinced now.
We have a load of Kubernetes stacks - but I feel they are overkill for most of your needs and the pods and replication has network latency, so I'm looking at more of a master-slave hot-swap high-availability strategy that will ultimately be cheaper, easier to understand and simpler to scale.
Another progress update. There is now a very basic firewall configuration UI to block IPs. You can use this to block connections to the mail server as well. In future releases, we will probably make this more dynamic. For example, just automatically block IPs for a specific period of time, if there are too many failed logged in attempts. We have to implement this across apps and the app logs are not too fail2ban friendly right now, so we have to see how we can do this.
There is also a mechanism to white list ports (will be documented) but there won't be a UI for this since I am not sure we should go about encouraging people to install things on Cloudron.
I think apart from some UI adjustments that @nebulon is making, we are set for the release!
@girish Just wanted to check for an update on this as I am really needing to store emails on a different location just like how apps work (my medical clinic clients are using email massively compared to before because of COVID-19 testing they've been doing the last few months, and the storage space usage is growing very quickly. I know you postponed the mail backup part where it was separated from box backups, but does this negatively impact the ability to store emails on an external disk too or is that feature still coming for storing emails on external disks?
I know you postponed the mail backup part where it was separated from box backups, but does this negatively impact the ability to store emails on an external disk too or is that feature still coming for storing emails on external disks?
Yes, we postponed the splitting up of box data and mail data. But moving mail to a separate disk is already possible. Just that box data also goes with it. This should not be a problem for your situation. Essentially, the directory
/home/yellowtent/boxdata(which contains the emails) can be moved anywhere you want. See https://cloudron.io/documentation/storage/#default-data-directory . Essentially, stop docker and cloudron, copy over all the stuff to new location, then just create a symlink to the new location.
(Just make sure you have backups, just in case). Note that the external disk has to be ext4.
@girish Dang, that's too bad. Thank you for confirming though. I'll keep that process in mind as something I can do when the time comes then (which I suspect will be in about 2 months or earlier), but hoping there'll be an easier way to still have the box data on the local disk rather than needing to move it in its entirety to a new disk. Just as how the app locations can be changed and it automatically moves the data, it'd be great if Cloudron could do that part too without needing a manual intervention for it. Plus it'd save a little bit of cost to the admin as they wouldn't need to create such a large external disk for it all, just for the emails.
The 5.6 pre-release is out. Only update if you are truly eager. We will roll this update out very slowly over this week and the next.
If you hit any issues, please do open separate threads. The docs are still getting fixed up, so let me know if you find something hard to follow.