Problems with CDO and UTF-7....

by Michael S. Kaplan, published on 2005/04/01 20:49 -05:00, original URI:

As long as I am linking the hell out of things this evening....

Dean Harding (a faithful reader and commenter of this blog), pointed out a problem with CDO and UTF-7 that has me wondering what the heck they are doing, too. He does post how he was able to work around it, in any case.

As he says: "I was having problems when trying to load an email message that contained body-parts encoded with the "unicode-1-1-utf-7" encoding. This encoding seems to be most popular with DSN (delivery status notification) messages, but theoretically any mail client should be able to encode with that encoding."

Thought I'd link to it for anyone who was interested....

And next time I decide to do this I will try combining several links into one post. Don't let the number of posts fool you, I am still feeling my way around this whole blogging thing. :-)

# pb on 4 Apr 2005 2:54 AM:

I discovered this problem a few months ago, reported to Microsoft via the ISV Buddy Program (great initiative!) and got the following response (edited):

"The error actually happens in ADO stream code. CDO has to tell the ADO stream when it's dealing with Unicode content. CDO recognizes "utf-7" but not >>unicode-1-1-utf-7<<".

# Heath Stewart on 4 Apr 2005 11:06 AM:

Hmm. An interesting encoding to say the least ( I could see why the lack of unicode-1-1-utf-7 in CDO could cause a problem when treated as UTF-7, though I must say I fail to understand the motivation for the encoding itself.

# Heath Stewart on 4 Apr 2005 1:29 PM:

Oops...I meant to say "when treated as US-ASCII" or whatever it may default to, since the characters in the US-ASCII range would be decoded as-is.

go to newer or older post, or back to index or month or day