@sam_uk I'm interested in this use case too. We want to incubate groups on our Cloudron until they've reached a size where they can afford their own.

@marcusquinn because it already exists

@luckow Yes, similar view to the aliases ones where all are listed for the mailbox user.

I would love this for the app images. Ideally a build which was made today from a git tag and made 10 days ago from the same git tag should result in the same docker image. But currently, it doesn't. I don't know if this is a solved problem for docker. If there's any docs/ideas here, would be good to know.

DNSBLs are configurable in 6.4

@fbartels I do believe you.

There is a "Spam" filter type in next release - 6.4

@girish what about just a normal organization level rights separation? I mean - it's really two different set of roles: 1st line support, dealing with mailboxes 2nd or 3rd, making sure the system and services are up and running. I don't need hiding anything, I just want to ensure my users can manage they mailboxes and users for they own. For now I have to temporary give admin permissions to the 1st line and that's kind of risky...

@girish WHOOP!!! Thank you!!

@fbartels Optimism and hope? /s Great points.

@murgero I didn't say it wouldn't be accessible; it would, just through my proxies, that make sure to remove any information, that would help in disclosure. You also miss an option with Intranets.

The latest lamp package support PHP 8.0

@fbartels This is a much better way to say it, yes. Some way to communicate with my users in a semi-permanent way.

@marcusquinn Yeah, I for one would love for my screw-ups and poking-arounds to be recorded. Would sure save time on re-Googling commands!

A simple feature to add with a decent benefit. +1!

@robi Thanks for letting me know.

I think @robin 's suggestion seems well thought out. The big advantage is that it would be totally optional to do it for apps for which it would be hard, while providing a significantly better UX for apps which do support it.