I do not believe there are well defined best practices for this space. Your concerns about emails are probably valid but if your team can try to maintain as close to a 100% pass rate then any dip should be noticed, it's only when there are constantly failing tests that no one is fixing that everything starts to be ignored. I think just like many development practices no matter how you report results this needs a single owner at the top, if you have a daily stand up then if there are any failing tests the lead should assign each of the fails to someone to fix, the next day ensure that they were fixed.
To help fix issues quickly appropriate logs, artifacts, etc. should be logged and easily available. In truth reporting is treated like an afterthought everywhere I've worked but it is a mistake. After all the time spent writing automated tests or performing manual tests the reporting is the only way other developers and managers actually see the return on the whole thing. Even if that means all of your tests are passing all the time that tells you something, that no one is breaking anything, and if the tests are all passing but things are actually breaking then that tells you the testing is not adequate. Yes the results may be 'boring' as you say if they rarely fail but they can also be useful for understanding the test coverage you have.
If no matter what you do everyone at the company ignores the test results, especially leaders, you have a cultural problem, that's far harder to solve than anything else, people want automation and more software but often don't want to invest in what 'watches the automation'. This needs to be solved because otherwise a lack of robustness will eventually come to ahead and then it's the poor people at the front line under stress (developers and testers) when really it was the leadership not paying attention and failing to ask, what's our health like? How are we testing? Results reporting makes that clear so you are right to think about it.
I am affiliated with an automated test results reporting provider called Tesults so beware of my bias but if you don't have anything set up to report results currently and want to focus on actually writing tests instead of writing reporting infrastructure it may interest you. You run your tests however you want with whatever framework and at the end of the test run have a script to upload your results, it stores all test results history, files, emails results out if you want it, and allows you to triage failing tests to team members. It is a commercial cloud based solution but I know they are currently exploring how to best provide service to open source projects with public views so if you are working on something like that the home page currently says to reach out.