There&#x27;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&#x27;ve explained a few times that when they&#x27;re sending 10MB+ attachments, <i>the other end of the email system</i> has a rule saying &quot;too big&quot;, and there&#x27;s nothing we can do at our end. Use a link or use smaller attachments. &quot;But it works fine for other recipients!&quot;. Yes, those email systems are administered by different groups.<p>This particular problem is not one that can be solved by hiding the details from the users; if they&#x27;re not going to trust me when I say &quot;just use sharing links, or if you have to, smaller attachments&quot;, 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).<p>But on the other hand, half the time when they come to me to have a return email error explained and it&#x27;s sitting right there in plain sight as to why, it&#x27;s also surrounded by paragraphs of boilerplate that only an admin can understand. I don&#x27;t blame them in those cases when they don&#x27;t successfully parse the only real English sentence in a couple of paragraphs of &#x27;line noise&#x27;.