December 5, 2003
Regarding your recent message.
Hi there. What can I do for you today?
> Your Email Client does not support MIME encoding.
Hmmm. Actually, it does support MIME encoding. That’s why I received the attached images you sent me. However, it doesn’t support non-standard, single-part encoding that your email client apparent mangles the text component of your message into. The fact that I can read the previous notice indicates that your client is quite capable of delivering multi-part content, but instead of encoding your original message as text, it inserted a generic warning instead.
Rather odd, wouldn’t you agree?
> Please upgrade to MIME-enabled Email Client.
Why? Just so I can read your messages? You must think they’re pretty darn important to warrant someone changing email clients just to read them. However, I suppose I could upgrade. I’d finally be able to view all the MIME-encoded spam that comes down the pipe along with the legitimate email. Thanks for the suggestion, but hitting the delete key is so much easier.
> (Almost every modern Email Client is MIME-capable)
First of all, what is the definition of ‘modern’ here? Quite frankly, being able to view HTML and rich media within an email client shouldn’t be a criteria for being modern. It should be a criteria for being bloated and a security risk. Secondly, being ‘capable’ of something doesn’t automatically imply being ‘functional’. Just because your client can send MIME-encoded messages, doesn’t mean you should. If you want me to read your messages, send them as plain text. If you want me to filter your messages, just keep on doing what you’re doing.
Thanks for stopping by.
This item was posted by .
Categories:
Leave a comment or send a trackback from your own site.