Apparently logcheck doesn't set a charset for the mail's contents in the
mail headers. This causes the mail software to misinterpret certain
messages. For instance, my system is set to a Spanish UTF-8 locale,
and gconfd's translated messages use non-ASCII characters; this causes
funny characters to appear in the mails I receive from logcheck:
Nov 22 12:54:23 localhost gconfd (jkohen-4008): Se recibió la señal
SIGHUP, recargando todas las bases de datos
If our MUAs work fine, you should see "se<A~><+->al" instead of
the expected "señal." Where <xy> are composed characters.
Assuming that all system processes and daemons run with the same locale,
adding the following header to the mails should fix this problem:
Content-Type: text/plain; charset="<system charset>"
Where the system charset is in the form US-ASCII, UTF-8, ISO-8859-1, etc.
Versions of packages logcheck depends on:
ii adduser 3.59 Add and remove users and groups
ii cron 3.0pl1-86 management of regular background p
ii debconf [debconf 1.4.40 Debian configuration management sy
ii debianutils 2.10.3 Miscellaneous utilities specific t
hi exim4 4.34-4 An MTA (Mail Transport Agent)
ii exim4-daemon-lig 4.34-5 Lightweight version of the Exim (v
hi lockfile-progs 0.1.10 Programs for locking and unlocking
ii logcheck-databas 1.2.31 A database of system log rules for
ii logtail 1.2.31 Print log file lines that have not
ii mailx 1:8.1.2-0.20040524cvs-1 A simple mail user agent
ii perl 5.8.4-2.3 Larry Wall's Practical Extraction
ii sysklogd [system 1.4.1-16 System Logging Daemon
Package: logcheck
Version: 1.2.31
Severity: wishlist
Hi,
Apparently logcheck doesn't set a charset for the mail's contents in the
mail headers. This causes the mail software to misinterpret certain
messages. For instance, my system is set to a Spanish UTF-8 locale,
and gconfd's translated messages use non-ASCII characters; this causes
funny characters to appear in the mails I receive from logcheck:
Nov 22 12:54:23 localhost gconfd (jkohen-4008): Se recibió la señal
SIGHUP, recargando todas las bases de datos
If our MUAs work fine, you should see "se<A~><+->al" instead of
the expected "señal." Where <xy> are composed characters.
Assuming that all system processes and daemons run with the same locale,
adding the following header to the mails should fix this problem:
Content-Type: text/plain; charset="<system charset>"
Where the system charset is in the form US-ASCII, UTF-8, ISO-8859-1, etc.
-- System Information: es_AR.UTF- 8 (charmap=UTF-8)
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.9
Locale: LANG=es_AR.UTF-8, LC_CTYPE=
Versions of packages logcheck depends on: 0.20040524cvs- 1 A simple mail user agent
ii adduser 3.59 Add and remove users and groups
ii cron 3.0pl1-86 management of regular background p
ii debconf [debconf 1.4.40 Debian configuration management sy
ii debianutils 2.10.3 Miscellaneous utilities specific t
hi exim4 4.34-4 An MTA (Mail Transport Agent)
ii exim4-daemon-lig 4.34-5 Lightweight version of the Exim (v
hi lockfile-progs 0.1.10 Programs for locking and unlocking
ii logcheck-databas 1.2.31 A database of system log rules for
ii logtail 1.2.31 Print log file lines that have not
ii mailx 1:8.1.2-
ii perl 5.8.4-2.3 Larry Wall's Practical Extraction
ii sysklogd [system 1.4.1-16 System Logging Daemon
-- debconf information: install- note:
logcheck/changes:
* logcheck/
--
Javier Kohen <email address hidden>
ICQ: blashyrkh #2361802
Jabber: <email address hidden>