CDO.Message utf-8 Problem

hellsa · November 25th, 2008, 11:16 PM

Hi All,

I have vbscript (ASP) code that sends emails using information passed into the script from a Flash component. The information is escaped using Flash's escape function so I receive the values properly and then decode them.

I can display the decoded information correctly in a web browser using UTF-8 encoding on the web page, however when I send the information via email the unicode values in the message body show the "funny" characters instead of what I expect. For example, when I look at the email sent by the script I see these three characters Ã¢â¬â instead of the em dash.

I've tried setting the charset for the email but it doesn't seem to have any effect.

Here's the my code:

Code:

      Set objMail = Server.CreateObject("CDO.Message")
      Set objBodyPart = objmail.BodyPart
      objBodyPart.Charset = "UTF-8" 

          Set objConf = Server.CreateObject("CDO.Configuration") 
          Set objFields = objConf.Fields

          With objFields
           .Item("schemas-forum won't allow urls") = 2
           .Item("schemas-forum won't allow urls") = "smtphost" 
           .Item("schemas-forum won't allow urls") = 20
           .Item("schemas-forum won't allow urls") = 25
           .Update 
          End With

          With objMail
              Set .Configuration = objConf
            .From = email
              .To = Trim(recip)
              .Subject = subject

          .TextBody = txtboilerplate   'the txtboilerplate contains the unicode chars
          End With

          objMail.Send
          Set objFields = Nothing
          Set objConf = Nothing
          Set objMail = Nothing

Is there something wrong with how I'm trying to set the charset?

Thanks!

riffraff · June 27th, 2009, 10:52 AM

Hi,

I am having similar problems, regarding sending email using cdo, with the Euro symbol incorrectly displayed.

Having Google'd this problem, it appears that asp 3.0 is a technology that is outdated, since the consensus seems to be that .net solves the problem since it is unicode compatible.

I am new to this forum and in fact new to the whole posting scenario, but since no one has replied to your post I assume that, the above correct.

Can anyone confirm or deny this assertion?

Old Pedant · June 28th, 2009, 11:02 PM

ASP is old and out of date, yes. But CDO isn't all that old and it *should* handle Unicode correctly.

But it may be that it just doesn't handle Unicode properly in a *TEXT* body. Have you tried using an HTMLBody, instead??

You make me want to go experiment with this. You say the Euro symbol doesn't come out right??

By the by: ASP *is* Unicode compatible and has been since it was first launched back in the late 1990s. Both VBScript and JScript--the two languages used with ASP--use *ONLY* Unicode internally! *ALL* characters in either language are always 16 bits (2 bytes) long. It's only when you output text or HTML from ASP code that a conversion from Unicode to the code page currently in effect takes place. There is one funny-odd (and stupid, really) limitation: The source code files used for ASP coding can *not* be Unicode. Go figure.