[mikezzz]

I have added a unit test and the store handles unicode fine as long as the caller encodes/decodes the bytes properly. I have tested it on evolution with some arabic characters and it worked ok. I did have to configure evolution to eplicitly encode using UTF-8.

Mike.

[acoliver]

Okay then it must be tbird or outlook.

[mikezzz]

I've been looking at the SMTP Sender code and that converts all of the bytes from the store into a string using "US-ASCII" encoding. Therefore it is possible that mails that are being forwarded on are incorrectly encoded. We probably should use new MimeMessage(mail.getRawInput()) to build the JavaMail message, but we will need to be careful to make sure that the whole excluded headers stuff is handled properly.

Mike.

[acoliver]

That's probably it. Can you file a bug for that against affects =>M3 fixed in M4 with a good description? That will be nasty once we get more easter adoption. Makes sense too since I could receive unicode and the subject was fine..just the body...