What's coming in 7.3

[girish]

Mostly quality of life improvements

What’s coming in 7.3

• (mail) Per mailbox quota - message limit and size
• (mail) VERP and bounce management for mailtrain and mautic
• SFTP export flag for volumes We will enhance the web file manager instead
• (mail) Virtual all directory in dovecot for search
• (mail) Expose mail queue operations
• (mail) wildcard aliases
• (mail) send as subaddress
• External app links in Dashboard
• storj/filebase integration
• Expose groups via LDAP
• Set domain of LDAP server
• Configurable TURN server
• Unify the app data and volumes code/ui
• Finish up async/await cleanup in backup code

[eganonoa]

@girish Brilliant work getting 7.1 out. No chance of the external turnserver in 7.2?

[girish]

@eganonoa ah yes, I have added it. It's not clear what is possible here but we plan to investigate.

[eganonoa]

@girish legend! Thank you!!!

I just left a message in that Nextcloud thread with my thoughts there: just go for one global setting to use or not use an external turnserver. Some apps allow for multiple turnservers (e.g. Nextcloud) but the format of how to add them differs per app (e.g. theoretically you can do it in Matrix but only if they share the same key, as there's only one place to add it). I reckon you will kill yourselves trying to find a per-app solution and really you can help loads of people who rely on external turn in various of your apps (e.g. jitsi, matrix, nextcloud, etherpad, etc) with a global solution. Once you have a working external turn on 443 why bother using anything else?

Also, note that anyone using your greenlight app probably already set up an external turn on 443 using the automated script that the BigBlueButton folks have (see https://github.com/bigbluebutton/bbb-install#install-a-turn-server.) And really you could probably just link to that in the docs to help people get set up with external turn with ease.

[girish]

@eganonoa yes, agreed. @nebulon probably has more info on this but he was looking into how to setup nginx streaming to turn server. This had the pre-requisite that the turn server be configurable to a separate domain as well.

[robi]

@girish not sure if you saw this post on this topic which suggests this is totally doable: https://forum.cloudron.io/post/44498

[eganonoa]

@robi problem for me is that I not only need 443 but also turn outside of cloudron irrespective because we stick cloudflare in front of all things cloudron. So irrespective adding an external turn has its uses.

[robi]

@eganonoa if you have advanced cloudflare features, then you can take care of that too.

[eganonoa]

@robi Business, not enterprise, so no Spectrum for TCP/UDP I'm afraid.

[robi]

@eganonoa okay, then possibly solved via VPN if all the clients are internal.

[jimcavoli]

LDAP groups would be huge. Been dying for that a couple years now

[eganonoa]

@robi That's what we do internally indeed. But we're spreading this out to our community now. So no dice. We must have an external turnserver.

[robi]

Volume backups option? Avoiding shared between N apps being backed up N times..

[girish]

@robi currently, volumes are not backed up at all.

[robi]

@girish can you add that to 7.3 or elsewhere?

[avatar1024]

Is there a plan for more backup backends like restic / borg for 7.3?

I recall it being listed for 7.2 at some point but looks like it got dropped off the list due to the need for a speedy release.

[girish]

@avatar1024 work has already started to split the backup code into separate formats, but I don't know if we can add a restic backend for 7.3 as such.