@marcusquinn Sounds like a good idea. I'm sure we can trust the wonderful Cloudron team with design decisions (and weighing those against technical feasability).

As long as they can make this happen - nag, nag 🙂

Right, we are actually fixing notification for the next release (6.3). In the meantime, Domains -> Renew all certs and then check the logs (button on the same page) if it fails. Usually, Let's Encrypt errors are temporary and currently Cloudron is a bit overzealous reporting those errors.

@atrilahiji I know that Elasticsearch is stopped developing, from opensource into enterprise. And do we develop Elasticsearch from the latest opensource version?

I'm curious about this. I could see this being useful for an educational institution that uses a cloudron for student accounts.

Looks like Haraka has a built-in web interface that could be a possible starting point here: http://haraka.github.io/plugins/watch/

For reference, Haraka has a greylisting function built in: http://haraka.github.io/plugins/greylist/ - and it works with the DNSWL / whitelist which we should enable too. That way if an IP is on the DNSWL, it automatically skips any greylisting attributes.

Just wanted to add that Haraka has both a DNSBL and a DNSWL, however it seems that the DNSWL is not enabled in the Haraka config yet, only the DNSBL is present.

http://haraka.github.io/plugins/dnswl/

It'd definitely be awesome if we could setup the DNSWL feature to allow a whitelist feed which then skips any DNSBL checks.

@girish I think the issue with MySQL Workbench is I can't use the latest version as they don't support macOS 10.14 past a certain version, and a colleague on a later macOS can get it working on a later MySQL Workbench version but I can't update my OS at the moment until some other software I use is updated to work with the later OS. Classic catch-22 on that one.

I think the solution to this should just be to use DBeaver, it's free on all platforms, and seems to work on all OS versions. too.

Maybe better to save your time for the odd additional /phpmyadmin/ that might be useful on certain apps.

Certainly appreciate the help and looking, but I don't want to distract you too much given it's a software version compatibility issue and not a Cloudron issue really. Thank you all the same though!!

@robi only the retention policy - https://docs.cloudron.io/backups/#retention-policy

@tamayers Ah, I understand the use case now. I will move this to Feature Request. It looks easy enough to add since we just need to disable the internal MX check.

@lucidfox AFAIK, since it's totally peer to peer, there is no risk. Of course, external users can use it but no data goes through your server.

@imc67 currently, there is no manual way to do it since it will get overwritten after restart.

@infogulch a hybrid of both would be best, but let's start with this one.

If CL is going to be more adopted in the enterprise, it will need better audit & retention capabilities before things go to archive.

@bestknownhost for a start to clarify, are you using an external backup storage or just the local disk for now? Using the local disk may cause disk usage to go up quickly depending on how much data you've put into the server.

If that is not the case, then you may have hit some issue we recently saw with mysql binlogs https://forum.cloudron.io/topic/4510/able-to-clean-up-binlog-files-in-var-lib-mysql-directory?_=1616402616926 ?

And as @robi mentioned, do you have any idea so far what is using all that disk space?

I have added it to https://docs.cloudron.io/profile/#api-tokens for a start. The API page is a bit outdated and will take more time to freshen up.

I love this conversation, this is gold.

We have to strengthen the mail server as a safe, it is a very valuable asset.

If we add to these limits/fuses the ability for the server to do certain actions if it detects that a domain has a higher percentage of X% of bounces and X% of complaints.

This would also be a must have to shield the mail server.

We have to be able to monitor all this well and automate actions in mail server.