Hi Jim, In dbmail.conf, please set:
[DBMAIL] .. TRACE_SYSLOG=5 because that way your errors will be more verbose and give you more clues to what's wrong. Once you have everything working, set the trace levels back down to level 2 or 3. and please review your application needs to figure out if you want to go all-utf8 or all-latin1. Then set your dbmail.conf and my.cnf to agree on the set of encodings that you will be using. This section in the MySQL has probably an overload of information, but is a good reference: http://dev.mysql.com/doc/refman/5.0/en/charset.html In a nutshell, in my.cnf, please set: [mysqld] character-set-server = utf8 default-character-set = utf8 (of course change utf8 to latin1 if you determine that you need latin1) Aaron On Fri, May 11, 2007, Jim McIver <[EMAIL PROTECTED]> said: > I'm a newbie and trying to make dbmail work with mysql 5.0.18 on > SLES10. I can't get a dbmail to connect to mysql. > > Message I get the log file is: > > collation mismatch, your MySQL configuration specifies a different > charset than the data currently in your DBMail database. > > show variables; yeilds > > | character_set_client | latin1 > | character_set_connection | latin1 > | character_set_database | latin1 > | character_set_results | latin1 > | character_set_server | utf8 > | character_set_system | utf8 > > I can't figure out how to get these all set to utf8? > > thx, > > -Jim McIver > > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
