Comment 2 for bug 124944

Revision history for this message
In , Javier Kohen (jkohen) wrote : Re: [Logcheck-devel] Bug#282534: logcheck: No contents' charset specified

Yes, it seems you're right about the merge.

Thanks,

maks attems wrote:
> reassign 282534 mailx
> thanks
>
> On Mon, 22 Nov 2004, Javier Kohen wrote:
>
>
>>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.
>
>
> well logcheck is using mail(1), so your wishlist applies to mailx.
> i guess this can be merged together with #207724?
>
>
>>ii mailx 1:8.1.2-0.20040524cvs-1 A simple mail user agent
>
>
> best regards.
>
> --
> maks
>
>

--
Javier Kohen <email address hidden>
ICQ: blashyrkh #2361802
Jabber: <email address hidden>