Lewis' Blog Tales from the trenches of information technology


Email proofreading

I suppose to some extent, we're all guilty of not proofing our own work well enough. The quickly dashed response; the (not recommended) text reply while <ahem> driving; the trigger finger on the Send button which sends our thoughts dashing into cyberspace just a few moments too soon...these are all examples of this condition, which is simply part and parcel of the high-speed, wide-bandwidth world in which most of us live and work.

However, there are times when this type of thing simply goes too far, and the responsibility rests squarely on the shoulders of the person sending the message to proof not only the content, but the headers, as well (and by "headers," I'm mainly referring to the list of recipient addresses, although a well-spelled subject is worth a few points, too).

I got an email this morning from someone at a client's office advising that "somewhere in the system, [his] email address [was] misspelled." Well, as GroupWise maintains its system-wide address book in concert with eDirectory, I knew this could not be the case. I advised him (naturally), that if someone were to send an email to a dozen people in the office including him, but that if his were the only misspelled address, the others would receive it. If just one of those people were to respond to all without proofing the recipient address list, his "broken" address would get circulated (and of course, he would not receive the reply).

True to form, he forwarded me an example of a "broken" message. The message, as it turns out, was sent from his own Palm Treo running Snappermail and his own sending address was misspelled in his Snappermail configuration, clear for all to see, including he, while composing the message in the first place. <sigh>

Naturally, this was my fault...

Tagged as: 1 Comment

Email Attachment Size

Why is it that people don't pay attention to sending email? I understand that there is a certain amount of ignorance to be expected in anything (and naturally, I now sound like a snob), but why is it that people just expect that if you can shove 30MB into the pipe at one end that the same size pipe is on the other, and server load be d-mned?