Comment 7 for bug 27121

Revision history for this message
In , Martin-Éric Racine (q-funk) wrote : Re: please encode headers according to RFC2047

Package: bsd-mailx
Version: 8.1.2-0.20081101cvs-2
Severity: normal

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

Come on! This bug has been open since 2003.

Meanwhile, practically everything in Debian has migrated to either using UTF-8
by default or acquired abilties to detect character-set and set MIME headers.

It so happens that several Release Goals in Debian relate to UTF-8 adoption.
Most of those goals were already achieved in previous Debian releases.

As such, this broken mailx implementation has become completely unacceptable.

Fixing it would require parsing LC_CTYPE and using the character-set it returns
to build the MIME headers used to produce the e-mail message.

- -- 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 bsd-mailx depends on:
ii base-files 5.0.0 Debian base system miscellaneous f
ii libc6 2.9-23 GNU C Library: Shared libraries
ii liblockfile1 1.08-3 NFS-safe locking library, includes
ii nullmailer [mail-transport-ag 1:1.04-1.1 simple relay-only mail transport a

bsd-mailx recommends no packages.

bsd-mailx suggests no packages.

- -- no debconf information

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

iEYEARECAAYFAkqdHpIACgkQeXr56x4Muc31DgCgjkjiBxMrFlA5AVOxO/WPJXoP
wvgAn3jX6oEbEd5thO/ZxXrEIhc/DI1b
=8FaF
-----END PGP SIGNATURE-----