Package: heirloom-mailx
Version: 12.4-1.1+b1
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

When piping text into heirloom-mailx, it fails to specify the charset used with
the From: line if the name inherited from /etc/passwd is in UTF-8. 

cat file | mail -s "some subject" u...@domain.ltd

q-funk:x:1000:1000:Martin-Éric Racine,,,:/home/q-funk:/bin/bash

Setting "set sendcharsets=utf-8" only seems to affect the MIME declaration that
appears in the message headers:

User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

However, it does not solve the above issue:

Message-Id: <1252199465.516755.6377.nullmai...@iki.fi>
From: Martin-?ric Racine <q-f...@iki.fi>

Yet, we see that:

$ file /etc/passwd
/etc/passwd: UTF-8 Unicode text

Is there something I'm missing?

- -- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-020630-generic (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages heirloom-mailx depends on:
ii  base-files               5.0.0           Debian base system miscellaneous f
ii  libc6                    2.9-25          GNU C Library: Shared libraries
ii  libgssapi-krb5-2         1.7dfsg~beta3-1 MIT Kerberos runtime libraries - k
ii  libssl0.9.8              0.9.8k-4        SSL shared libraries

heirloom-mailx recommends no packages.

Versions of packages heirloom-mailx suggests:
ii  nullmailer [mail-transport-ag 1:1.04-1.1 simple relay-only mail transport a

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqjD5EACgkQeXr56x4Muc3csgCfTAG3dc6f83Va4obf7AxgCKvv
zicAn2ZsQes2yjLcRJipIsz3Hkhfywv0
=N5oH
-----END PGP SIGNATURE-----



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to