We plan to operate a shared mail server than can be used by users of the domain and we will work to ensure it is trusted by imposing usage limits. We will assume that every endpoint in our domain is someone's personal homelab, meaning small-scale use. For large mailing campaigns and newsletters there are plenty of services to choose from that enable those but for just sending personal emails, it should work.
Wait, so self hosting but I don't host my own email? So you guys just want to run your own mailserver and give people custom emails?
That sounds like negative utility. That would make hosting an email server on one of your domains harder than hosting it on a .com, so what benefit is this providing?
One of the biggest problems people have when self-hosting their own mail servers is delivery issues because the big email providers don't trust your server. The goal with the shared mail server is to create a server that is trusted by those providers and then making it accessible to users of the .self TLD so they can forward their mail to it and have confidence it will be delivered. It would act only as a relay, users would still self-host their own mailboxes. And nothing would force you to use it.