Exposing this in the backup UI is the idea.. not fishing in the logs.

@d19dotca Perhaps even a per-app option, as in "Check for spam sent from this app."

I've upvoted this because it's always nice to know about other options. But I don't know enough to know if this really could replace solr.

That's great work @girish - it's not often you step out for the day and return to see your post "solved". I was going to include that it should be a simple nginx config thing but I know better. And it's unfortunate the request caching is a nightmare to enforce "must-staple".

Regardless, the win here is that you have it enabled. That should now be reflected in test reults from Mozilla Observatory (extended to Qualys SSL Labs & ImmuniWeb). Thanks for putting in the grunts on this one.

I like both the suggestions! Will look into adding them.

@imc67 nevermind, I found it - https://docs.espocrm.com/user-guide/mass-email/#settings

I will move this to feature request. But we haven't really analyzed what work this involves.

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.

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.

@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

@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.

@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.

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.

I just realized part of this is a duplicate of one that @marcusquinn filed earlier for Add a setting for sendmail limits per mailbox per day

@girish said in See volume disk space usage on System Info:

This is fixed in 6.1 - https://git.cloudron.io/cloudron/box/-/issues/756

I see one of my volumes (an ext4 Hetzner Cloud Volume), but not the other (CIFS Hetzner Storage Box).

Is there any way to display disk usage of CIFS mounts too?

Thanks!

@nebulon Sorry, totally missed your line about the shortcuts in the previous message 🤦 my bad

@nebulon My thinking for write protection was actually that it could - literally - use filesystem permissions rather than introducing a database. Check if the file is writable before deleting/writing, and fail if it isn't writable (or offer to override, which will have to chmod +w it)