Prior to this release, if the email was 8bit encoded and contained a charset attribute, non ascii characters were corrupted in the original email.
Any non ascii characters in the signature were rendered correctly.

Example of encoding and charset in affected emails:

This issue was resolved in Version 4.02

Related Products: CMS DOM v4