https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8042
--- Comment #4 from Henrik Krohns <[email protected]> --- Or if the problem is the actual perl $token variable being in UTF8 mode fed to bind_param, is not the logical solution to utf8::encode it? mysql_enable_utf8 "When set, a data retrieved from a textual column type (char, varchar, etc) will have the UTF-8 flag turned on if necessary. This enables character semantics on that string." Seems a radical change in general character semantics for the code. So I question if it's the correct fix. -- You are receiving this mail because: You are the assignee for the bug.
