@nebulon said in Change request: Notifications in Cloudron 3.5.1:
We have explicitly made email status notifications sticky until resolved. We have done that, since most apps are able to send out emails and thus those mails would always end up in spam or right out get denied by the receiving email server if those things are not setup. So in your case you don't care about such emails being lost? If there are good reasons to not nag the user about those issues, we can add some "ignore" setting I guess. Maybe you can describe your use-case about this a bit further.
I understand why you do this. For me, these are issues I am aware of.I wouldn't use my Cloudron email server for critical issues for this exact reason. If I need a better assurance that my e-mail can be transmitted, I would do what msbt does - use an external smtp server.
Since I self host, it is not possible for me to get a PTR record (since my ISP uses dynamic IP's, they don't offer this functionality). So for me, the cloudron mail server is basically a place where I can receive email notifications from different automated tasks/service, and where I can live with the reliability issues.
For me, the preferred fix would be an ability to either block these setup warnings, or to have the functionality msbt describes, if setting an external smtp server would be considered a valid setup by the email notification system. It's not a big sacrifice for me to use an external smtp, although I would prefer not to (the allure of completely self hosting, and not leaving any traces on external services for private notifications from private automated services is a big "privacy plus" for me).
Also, I would like it if the email notification was satisfied with being "off" for domains that don't have email configured (at least if the Cloudron is setup with at least one working email domain).
Thanks for looking into this so quickly