On Thu, 16 Jun 2011 16:38:49 +0200 Nenad Cimerman <ncimer...@googlemail.com> wrote:
TLDR: some time in the last 15 years, this bug against logcheck has been fixed, as far as i can tell > My system is setup with non-POSIX default locale (see below), using UTF-8 > character encoding. > This leads to many lines inside various log files (e.g. /var/log/syslog) > containing 'german umlaut' characters (äöüÄÖÜß). > ........Details....... > > The script /usr/sbin/logcheck is usually run by the cron deamon, based on > /etc/cron.d/logcheck. This process runs in POSIX locale (LC_ALL=POSIX, > LANG=POSIX), despite /etc/default/locale being possibly set to a different You can set a different LANG in logcheck.conf if you need > Inside /usr/sbin/logcheck, the function sendreport() uses mail(1) or nail(1) logcheck now uses mime-construct(1) instead of either of these > By default, reports are sent 'inline' (not as an attachment) This can also be controlled with the MAILASATTACH option > Unfortunately mail(1) is responsible for the characterset issue, as it does > ignore the locale settings completely. mime-construct allows the charset to be set using the MIMEENCODING option in logcheck.conf So i think we can close this bug.
