Linked by Thom Holwerda on Thu 12th Apr 2012 08:59 UTC
Permalink for comment 513933
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2005-07-11
Standard compliance is pretty good these days, even in Exchange. I can't vouch for the billion badly coded email clients but that's not an email problem, that's a code-quality problem.
Content is encoded in exactly one way: MIME. "
But, is that Microsoft's implementation of MIME? A non-MS implementation of MIME?
What about those still using "quoted-printable" instead?
And what about those using TNEF instead of MIME?
And is that using MS pseudo-HTML? Or real HTML? Or someone else's bastardised HTML (like FirstClass mail)?
There's not "1 single, standard method" for encoding even the text in an e-mail, let alone the "HTML" formatting, or even the attachments.