@lonk no, monthly doesn't make sense apart from an email, like the new Cloudron release emails.
Weekly maybe, but ideally the day it is released.
From there those interested in those can subscribe to the stable Apps or unstable Apps notifications.
I like that. Opting into app updates without having them installed. Often times user's don't want to be the early adopters (I do, but I'm me 😂) so they wouldn't install anything initially, and getting release notifications even though the app isn't installed might eventually prompt them to. It's not even too difficult a change since it already exists for installed apps.
Thank you for the quick reply. But even in my testing environment, telling me my backup method is unsafe once a day is just a hassle to weed them out of the Cloudron update (valuable) notifications. I bet I can just trick Ubuntu into seeing the path as a volume to get rid of the notification.
But for normal Cloudron users, I bet an option to acknowledge and disable the “backup is unsafe notification” would be valuable for them especially in their first non-production use of Cloudron (where I’m personally at for now).
@JOduMonT Currently, the 'email is not configured properly' notification is updated every 30 minutes. So, it's very much possible that those email settings are fine now and that notification will go away after 30 minutes.
If you click on the notification, it should expand to give information on what exactly is not setup properly. Can you tell me what you see if you click the notification ?
Also, zen.spamhaus.org being disabled is not good! Do you have a custom DNS setup by any chance? Under system -> services, is unbound running OK?
@girish As far as I know, it's correct - unless DKIM has the IP included, since that did change during the migration. Unfortunately, the Email section of Cloudron wasn't properly giving the needed information - previously it was saying DKIM was incorrect, but the display just said something like "expected null to equal null". DKIM isn't showing in the Email status page at all with the workaround I added here.
I'll put that in as a separate issue, though, once the update comes out and I see the proper message.