# Ensure only problem-free chatmail servers are suggested on the public list by monitoring **URL:** \ **Category:** Chatmail Relays\ **Created:** [July 19, 2026, 4:10pm UTC](https://forum.delta.chat/t/ensure-only-problem-free-chatmail-servers-are-suggested-on-the-public-list-by-monitoring/5557 "2026-07-19T16:10:12Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![ian](https://forum.delta.chat/user_avatar/forum.delta.chat/ian/32/3164_2.png) [@ian](https://forum.delta.chat/u/ian)\ **Post date:** [July 19, 2026, 4:10pm UTC](https://forum.delta.chat/t/ensure-only-problem-free-chatmail-servers-are-suggested-on-the-public-list-by-monitoring/5557/1 "2026-07-19T16:10:13Z")
The service level availability of some of the entries may degrade over time, they may not see regular updates or they may be plagued by unfixed configuration issues that compromise their ability to fully participate in the federation. Independent, third party automation could keep checking the health of each according to standardized criteria and alert the list maintainers and the given relay operator in case of issues. The list maintainers should either mark the entries that never have problems as suggested or remove problematic ones. As an alternative, the measured metrics and the list of issues found could be summarized in a table automatically. Via: > [@Provide feedback on the user interface when hidden control messages result in error](https://support.delta.chat/t/provide-feedback-on-the-user-interface-when-hidden-control-messages-result-in-error/5553/2): > > Thank you! I also believe published chatmail relays in [Chatmail: Relays](https://chatmail.at/relays) should be periodically tested by an automatized process (such as it happens with R packages published on CRAN, for which there are regular CRAN checks) which would unpublish those failng such as the one causing the issue. --- _[View the full topic](https://forum.delta.chat/t/ensure-only-problem-free-chatmail-servers-are-suggested-on-the-public-list-by-monitoring/5557)._