#282534 logcheck: No contents' charset specified

Package:
bsd-mailx
Source:
bsd-mailx
Description:
simple mail user agent
Submitter:
Javier Kohen
Date:
2013-10-06 08:21:15 UTC
Severity:
wishlist
#282534#5
Date:
2004-11-22 20:46:41 UTC
From:
To:
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.
#282534#10
Date:
2004-11-25 22:41:18 UTC
From:
To:
reassign 282534 mailx
thanks

well logcheck is using mail(1), so your wishlist applies to mailx.
i guess this can be merged together with #207724?

best regards.
#282534#17
Date:
2004-11-26 03:25:24 UTC
From:
To:
Yes, it seems you're right about the merge.

Thanks,

maks attems wrote:
#282534#24
Date:
2006-01-18 11:51:26 UTC
From:
To:
Should this really be a wishlist item? It may not exactly be a major
bug, but it does cause flawed e-mails to be produced and sent, some of
them probably unreadable by the reciever without manually finding out
and selecting the correct encoding.