Linked by Thom Holwerda on Thu 12th Apr 2012 08:59 UTC
Internet & Networking I would honestly serve at the altar of the person that did this. Keep the debugging information, but for the love of god, make your email client do something pretty and useful with it.
Permalink for comment 513829
To read all comments associated with this story, please click here.
Member since:

So, he wants to strip out which server rejected the e-mail, the last server in the chain that transmitted it, the stated reason for rejection, and any information to uniquely identify the e-mail beyond subject. Notably, it leaves off the acceptable attachment size limit, which, IMHO, is a bit useful for resending.

The first suggestion is to compress the file, which, is unlikely to help as it's an image and he needs 30% compression. The second is a link, which is more of an advertisement than anything. The third assumes the recipient uses iMessage, which is unlikely and will confuse people such as the author when it fails to work.

"User friendly" error messages are nice if they're useful. Modern software tends to sacrifice the later for the former. It either hides any information that might be useful in fixing the bug, or jumps to inaccurate conclusions so it can hold your hand while it leads you on a wild goose chase. Hiding useful information keeps users ignorant, and prevents them from solving their own problems (while learning in the process).

That said, some people hate to learn. They want the computer to make a 45 MB e-mail go through, rather than learn why it's a bad idea to e-mail such a monstrosity. The author states "I can barely read that email" when it has three sentences and the specific error as the first line of the debug information. IMHO, rather than save space by eliminating useful information from bounce messages, he could have omitted the last two words of that quote.

Reply Score: 6