But, by all means, improve the text itself.
But, by all means, improve the text itself.
Machines can read [these error messages] just fine, though.
Here's an idea: machines shouldn’t slap us in the face.
They should help us along if they fail to do our bidding.
He's not encouraging admins to replace useful debugging output. In fact, it's the opposite: he's encouraging email client designers to actually use the debugging output to let people know what went wrong. His mockup is quite clearly of an email client showing users relevant recovery options based on an underlying error message the client has parsed.In other words, he's proposing that email clients treat MTA error messages precisely as they already handle raw headers. Full headers contain useful debugging information, but you aren't normally debugging.
Maybe there should be, but that's a problem that has to be solved before the shiny UI can be placed over it.
If you've written many systems that deal with email you know that you could be processing almost anything.
Sure, there might not be a 'standard' format for email, but you can return a multipart message that perserves the ugly text messages and includes an HTML message for the rest of us.
Note, that by standard I mean most emails violate any particular email RFC in some egregious way, similar to the way most HTML pages are invalid, for example the page for this comment has no less than 20 errors.
The text can and should be improved and be void of HTML shiny - the mail client itself could parse the new, slimmer, standard error text and make it pleasing.
As somebody who spent 13 years doing tech support I can tell you that the vast majority of users don't read error messages no matter how shiny or well written they are.
If the user has made a mistake somewhere, the client should try to understand the error message and, if it's user error (email address doesn't exist, attachment too big), it should suggest solutions to the problem in a language the user can understand.
If the system itself has an issue, the client should provide enough information to tell the user either: a) How they can resolve it b) How they can contact whoever needs to resolve it
Easy-to-read message at the top, debug output underneath. Simple.
This means the OP's solution can leave useful debugging in place while providing the user with the HTML shiny they've come to expect.
Let's standardize all email error messages to HTML. At least then a standard exists even though it will suck, most standards suck in many ways. But it's a total nightmare without any.
Does any mail client handle the mime-type text/markdown or text/x-markdown [0] or text/x-web-markdown [1] or something?
[0] http://www.mail-archive.com/markdown-discuss@six.pairlist.ne...
[1] http://codecraft.io/2011/07/18/ubuntu-markdown-files-mime-ty...