On Sun, 2007-07-08 at 17:10 +0545, Tek Bahadur Limbu wrote: > > After putting the password in dbmail.conf, I get yet another error: > > [EMAIL PROTECTED] dbmail-users -a john -w john123 > > Error collation mismatch, your MySQL configuration specifies a > different charset than the data currently in your DBMail database. > Failed. Could not connect to database (check log) > Command failed. > > I have the following in my dbmai.conf: > > # > # encoding must match the database/table encoding. > # > encoding = utf8 > > # > # messages with unknown encoding will be assumed to have > # default_msg_encoding > # > default_msg_encoding = utf8 > > # > > I changed both to latin1 and now it works!! >
You should create new databases in utf8. Drop the tables, go into my.cnf and change from latin1 to utf8, then re-create the tables. DBMail's dbmail_msg_encoding is unrelated to the database encodings. It has to do with messages that come without correct headers. If you receive large numbers of emails from local users in a specific language, but without message headers indicating the language, then we'll fall back onto the default_msg_encoding to try to make sense of the message. Aaron PS - Are you writing to us from Nepal? _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
