------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=980 Summary: Allow to specify mysql connection charset Product: Exim Version: N/A Platform: All OS/Version: All Status: NEW Severity: wishlist Priority: medium Component: General execution AssignedTo: [email protected] ReportedBy: [email protected] CC: [email protected] I'm using exim4 with vexim, but I've modified the latter a little to be unicode-aware, meaning it now stores and retrieves data in UTF-8. However, it appears that there is no way to tell Exim 4 what character set to use when talking to the MySQL server, and that results in e.g. broken vacation messages (all characters that don't fit into latin1 are being converted to questionmarks). It seems that a similar problem with PostgreSQL is being addressed in bug 508, and a solution was proposed there to add an additional config option (pg_encoding). I think this would work here too, if a similar option were also added to mysql. Alternatively, here are a few alternatives: *) allow specifying character set in mysql_servers and pgsql_servers (also in oracle_servers and ibase_servers if relevant); *) add a separate config option, but make it more generic. For example, allow Exim administrator to specify some queries that would be executed each time a new SQL connection is established -- Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email -- ## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
