There's definitely a balance to be struck here. I work at a small company where I routinely get asked by the sales staff as to why the email is broken and their

There's definitely a balance to be struck here. I work at a small company where I routinely get asked by the sales staff as to why the email is broken and their emails are getting rejected. I've explained a few times that when they're sending 10MB+ attachments, the other end of the email system has a rule saying "too big", and there's nothing we can do at our end. Use a link or use smaller attachments. "But it works fine for other recipients!". Yes, those email systems are administered by different groups. This particular problem is not one that can be solved by hiding the details from the users; if they're not going to trust me when I say "just use sharing links, or if you have to, smaller attachments", then the users have to at least understand that email is a federated sytem, not a centralised system (perhaps not those exact terms, but the concepts). But on the other hand, half the time when they come to me to have a return email error explained and it's sitting right there in plain sight as to why, it's also surrounded by paragraphs of boilerplate that only an admin can understand. I don't blame them in those cases when they don't successfully parse the only real English sentence in a couple of paragraphs of 'line noise'.