Encoding problem after AppendMessage()

Hi,

I have a scenaio where I have to change the subject of a message in the inbox folder and then move it to another mailbox folder. When I do it in our development environment, it seems to be working just fine (Exchange 2007), but when I do it at one of our clients (Exchange 2003) some wierd stuff happens to the encoding of both the subject and the body.

If the subject contains a word with a danish character in it 'æøå', for instance 'Bemærkning', then the subject just becomes 'B'. If the body contains any danish characters, they are replaced by '�'.

The subject-problem occures on both plain-text mails and html mails, but I have only seen the body-problem on plain-text mails.

My approach is to fetch the message, alter the subject, add the message to the new mailbox folder using ExchangeClient.AppendMessage(), and delete the original. I have tried setting the PreferredTextEncoding to 'iso-8859-1', but that didnt help.

What am i doing wrong?

Also, is there a way to alter the subject of a message directly without having to fetch it first? If I alter the subject on a fetched message and then uses ExchangeClient.Move(), the new subject is not included.

Im using WebDav and IMAP.

/AndreasK

Hi Andreas,


Please accept my apology for the delayed response.

We are currently looking into the said issue and we will soon reply back with more updates on this. In meanwhile, could you please confirm the following on your end,
  • Append a message having danish symbols in subject. In this case please append the message without modifying the subject. Check if your results are correct.

For clarification, ExchangeClient.Move method will simply move the message to any other folder of Exchange Inbox. In this case the modifications will not reflect in the resultant message. If you want to modify the contents of the message and then add it some folder of Inbox then you have to use the ExchangeClient.Append method.

We may need a sample message and code snippet from your end to look deeply into this issue. If possible, please provide this information with your next reply.

Regards,