Am 12.09.2013 14:18, schrieb Bastian: > Am 12.09.2013 14:07, schrieb Michael Schwartzkopff via amavis-users: >> >> Am Donnerstag, 12. September 2013, 14:03:14 schrieb Bastian via >> amavis-users: >> >> > Am 12.09.2013 13:55, schrieb Patrick Ben Koetter via amavis-users: >> >> > > * Bastian via amavis-users <[email protected]>: >> >> > >> Hi there, >> >> > >> today i did an upgrade from squeeze to wheezy, resultin in an amavis >> >> > >> update to version 2.7.1-2, and mysql is now 5.5. >> >> > >> I am logging amavis mails to mysql, but after the update, german >> umlauts >> >> > >> look like this: >> >> > >> >> >> > >> mysql> select subject from amavis.msgs where subject like "%und >> >> > >> fusionen%" ; >> >> > >> >> +----------------------------------------------------------------+>> >> >> > >> | subject | >> >> > >> >> >> > >> +----------------------------------------------------------------+ >> >> > >> >> >> > >> | Übernahmen und Fusionen - Schäppchenjagd für Anleger? | >> >> > >> | Übernahmen und Fusionen - Schäppchenjagd für Anleger? | >> >> > >> >> >> > >> +----------------------------------------------------------------+ >> >> > >> 2 rows in set (0.01 sec) >> >> > >> >> >> > >> The second mail was logged before the update. Can someone please >> give me >> >> > >> a hint what the problem could be, >> >> > >> and if it is related to amavis, how to resolve this? The DB >> collation >> >> > >> did not change. >> >> > > >> >> > > The default locale on your system changed. Set the locale >> explicitly in >> >> > > your MySQL amavisd database. >> >> > > >> >> > > p@rick >> >> > >> >> > The default locale (hope this is the right config file?!) did not >> change: >> >> > >> >> > root@gate1:~# cat /etc/default/locale >> >> >> >> no. Patrick ment something like: >> >> >> >> http://dev.mysql.com/doc/refman/5.0/en/locale-support.html >> >> >> > > I missed an error message when restarting mysql, and had to change > following setting in my.cf: > > < language = /usr/share/mysql/english > > lc-messages-dir = /usr/share/mysql > > Now it is working again! > Thanks for your help! > > Bastian
Hmm... sorry, this did not solve the problem :( Bastian
