Re: [Mutt] #3172: mutt-1.5.16: handling of RFC2047 incompatible

To: mandas@xxxxxxxxxx, pdmef@xxxxxxx, vincent@xxxxxxxxxx
Subject: Re: [Mutt] #3172: mutt-1.5.16: handling of RFC2047 incompatible
From: Mutt <fleas@xxxxxxxx>
Date: Tue, 27 Jan 2009 15:29:46 -0000
Auto-submitted: auto-generated
Cc: mutt-dev@xxxxxxxx
In-reply-to: <071.1d2242dfb90fb4460d1ed76b27f24993@xxxxxxxx>
List-post: <mailto:mutt-dev@mutt.org>
List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-dev"
Mail-followup-to: fleas@xxxxxxxx
References: <071.1d2242dfb90fb4460d1ed76b27f24993@xxxxxxxx>
Reply-to: fleas@xxxxxxxx
Sender: owner-mutt-dev@xxxxxxxx

#3172: mutt-1.5.16: handling of RFC2047 incompatible headers
------------------------------------------------------+---------------------
  Reporter:  Dimitris Mandalidis <mandas@xxxxxxxxxx>  |       Owner:  mutt-dev
      Type:  defect                                   |      Status:  closed  
  Priority:  major                                    |   Milestone:          
 Component:  mutt                                     |     Version:          
Resolution:  duplicate                                |    Keywords:          
------------------------------------------------------+---------------------
Changes (by pdmef):

  * status:  new => closed
  * resolution:  fixed => duplicate


Old description:

> {{{
> Package: mutt
> Version: 1.5.16
> Severity: normal
>
> -- Please type your report below this line
> Some mail user agents generate incorrect headers when supplying non-ascii
> information, so instead of RFC2047-compatible ?=charset?enc?text?=, raw
> non-ascii data or escape'd octal values are supplied.
>
> However, IMHO mutt should take this into account when replying to such a
> message with $edit_headers=yes as in this case it supplies the $editor
> with
> data which may not lie within $charset, and confuse editors with file
> encoding auto-sensing.
>
> Currently, it seems that mutt prints the malformed header as-is in the
> temporary file the editor opens while it correctly iconv()s the proper
> ones.
> Perhaps, mutt should replace the not properly encoded data with, say, '?'
> as
> there 's no reason to catch every possible case.
>
> -- System Information
> System Version: Linux lizard 2.6.27.12 #1 SMP Sun Jan 25 13:27:39 EET
> 2009 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AuthenticAMD
> GNU/Linux
>
> -- Build environment information
>
> (Note: This is the build environment installed on the system
> muttbug is run on.  Information may or may not match the environment
> used to build mutt.)
>
> - gcc version information
> i686-pc-linux-gnu-gcc
> Using built-in specs.
> Target: i686-pc-linux-gnu
> Configured with: /var/tmp/portage/sys-
> devel/gcc-4.1.2/work/gcc-4.1.2/configure --prefix=/usr --bindir=/usr/i686
> -pc-linux-gnu/gcc-bin/4.1.2 --includedir=/usr/lib/gcc/i686-pc-linux-
> gnu/4.1.2/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2
> --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2/man
> --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2/info --with-gxx-
> include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include/g++-v4
> --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec
> --enable-nls --without-included-gettext --with-system-zlib --disable-
> checking --disable-werror --enable-secureplt --disable-multilib --enable-
> libmudflap --disable-libssp --disable-libgcj --with-arch=i686 --enable-
> languages=c,c++,objc,treelang --enable-shared --enable-threads=posix
> --enable-__cxa_atexit --enable-clocale=gnu
> Thread model: posix
> gcc version 4.1.2 (Gentoo 4.1.2 p1.1)
>
> - CFLAGS
> -Wall -pedantic -O2 -march=athlon64 -pipe -fomit-frame-pointer -msse3
>
> -- Mutt Version Information
>
> Mutt 1.5.16 (2007-06-09)
> Copyright (C) 1996-2007 Michael R. Elkins and others.
> Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
> Mutt is free software, and you are welcome to redistribute it
> under certain conditions; type `mutt -vv' for details.
>
> System: Linux 2.6.27.12 (i686)
> ncurses: ncurses 5.6.20061217 (compiled with 5.6)
> Compile options:
> -DOMAIN
> -DEBUG
> -HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE
> -USE_FCNTL  +USE_FLOCK   -USE_INODESORT
> -USE_POP  +USE_NNTP  -USE_IMAP  +USE_SMTP  -USE_GSS  +USE_SSL_OPENSSL
> -USE_SSL_GNUTLS  -USE_SASL  +HAVE_GETADDRINFO
> -HAVE_REGCOMP  +USE_GNU_REGEX
> +HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET
> +HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM
> +CRYPT_BACKEND_CLASSIC_PGP  -CRYPT_BACKEND_CLASSIC_SMIME
> +CRYPT_BACKEND_GPGME
> -EXACT_ADDRESS  -SUN_ATTACHMENT
> +ENABLE_NLS  -LOCALES_HACK  +COMPRESSED  +HAVE_WC_FUNCS
> +HAVE_LANGINFO_CODESET  +HAVE_LANGINFO_YESEXPR
> +HAVE_ICONV  -ICONV_NONTRANS  -HAVE_LIBIDN  +HAVE_GETSID  +USE_HCACHE
> -ISPELL
> SENDMAIL="/usr/sbin/sendmail"
> MAILPATH="/var/spool/mail"
> PKGDATADIR="/usr/share/mutt"
> SYSCONFDIR="/etc/mutt"
> EXECSHELL="/bin/sh"
> MIXMASTER="mixmaster"
> To contact the developers, please mail to <mutt-dev@xxxxxxxx>.
> To report a bug, please visit http://bugs.mutt.org/.
>
> vvv.nntp
> patch-1.5.6.dw.pgp-timeout.1
> patch-1.5.6.dw.mbox-hook.1
> patch-1.5.16.rr.compressed.1
> patch-1.5.4.lpr.collapse_flagged Lukas P. Ruf <lukas.ruf@xxxxxx>
> }}}

New description:

 {{{
 Package: mutt
 Version: 1.5.16
 Severity: normal

 -- Please type your report below this line
 Some mail user agents generate incorrect headers when supplying non-ascii
 information, so instead of RFC2047-compatible ?=charset?enc?text?=, raw
 non-ascii data or escape'd octal values are supplied.

 However, IMHO mutt should take this into account when replying to such a
 message with $edit_headers=yes as in this case it supplies the $editor
 with
 data which may not lie within $charset, and confuse editors with file
 encoding auto-sensing.

 Currently, it seems that mutt prints the malformed header as-is in the
 temporary file the editor opens while it correctly iconv()s the proper
 ones.
 Perhaps, mutt should replace the not properly encoded data with, say, '?'
 as
 there 's no reason to catch every possible case.

 -- System Information
 System Version: Linux lizard 2.6.27.12 #1 SMP Sun Jan 25 13:27:39 EET 2009
 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AuthenticAMD GNU/Linux

 -- Build environment information

 (Note: This is the build environment installed on the system
 muttbug is run on.  Information may or may not match the environment
 used to build mutt.)

 - gcc version information
 i686-pc-linux-gnu-gcc
 Using built-in specs.
 Target: i686-pc-linux-gnu
 Configured with: /var/tmp/portage/sys-
 devel/gcc-4.1.2/work/gcc-4.1.2/configure --prefix=/usr --bindir=/usr/i686
 -pc-linux-gnu/gcc-bin/4.1.2 --includedir=/usr/lib/gcc/i686-pc-linux-
 gnu/4.1.2/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2
 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2/man
 --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2/info --with-gxx-
 include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include/g++-v4
 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec
 --enable-nls --without-included-gettext --with-system-zlib --disable-
 checking --disable-werror --enable-secureplt --disable-multilib --enable-
 libmudflap --disable-libssp --disable-libgcj --with-arch=i686 --enable-
 languages=c,c++,objc,treelang --enable-shared --enable-threads=posix
 --enable-__cxa_atexit --enable-clocale=gnu
 Thread model: posix
 gcc version 4.1.2 (Gentoo 4.1.2 p1.1)

 - CFLAGS
 -Wall -pedantic -O2 -march=athlon64 -pipe -fomit-frame-pointer -msse3

 -- Mutt Version Information

 Mutt 1.5.16 (2007-06-09)
 Copyright (C) 1996-2007 Michael R. Elkins and others.
 Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
 Mutt is free software, and you are welcome to redistribute it
 under certain conditions; type `mutt -vv' for details.

 System: Linux 2.6.27.12 (i686)
 ncurses: ncurses 5.6.20061217 (compiled with 5.6)
 Compile options:
 -DOMAIN
 -DEBUG
 -HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE
 -USE_FCNTL  +USE_FLOCK   -USE_INODESORT
 -USE_POP  +USE_NNTP  -USE_IMAP  +USE_SMTP  -USE_GSS  +USE_SSL_OPENSSL
 -USE_SSL_GNUTLS  -USE_SASL  +HAVE_GETADDRINFO
 -HAVE_REGCOMP  +USE_GNU_REGEX
 +HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET
 +HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM
 +CRYPT_BACKEND_CLASSIC_PGP  -CRYPT_BACKEND_CLASSIC_SMIME
 +CRYPT_BACKEND_GPGME
 -EXACT_ADDRESS  -SUN_ATTACHMENT
 +ENABLE_NLS  -LOCALES_HACK  +COMPRESSED  +HAVE_WC_FUNCS
 +HAVE_LANGINFO_CODESET  +HAVE_LANGINFO_YESEXPR
 +HAVE_ICONV  -ICONV_NONTRANS  -HAVE_LIBIDN  +HAVE_GETSID  +USE_HCACHE
 -ISPELL
 SENDMAIL="/usr/sbin/sendmail"
 MAILPATH="/var/spool/mail"
 PKGDATADIR="/usr/share/mutt"
 SYSCONFDIR="/etc/mutt"
 EXECSHELL="/bin/sh"
 MIXMASTER="mixmaster"
 To contact the developers, please mail to <mutt-dev@xxxxxxxx>.
 To report a bug, please visit http://bugs.mutt.org/.

 vvv.nntp
 patch-1.5.6.dw.pgp-timeout.1
 patch-1.5.6.dw.mbox-hook.1
 patch-1.5.16.rr.compressed.1
 patch-1.5.4.lpr.collapse_flagged Lukas P. Ruf <lukas.ruf@xxxxxx>
 }}}

--

Comment:

 Yes, this is a dupe of #2009 and is fixed in the latest version using
 $assumed_charset which should cover header and body.

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3172#comment:3>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

References:
- [Mutt] #3172: mutt-1.5.16: handling of RFC2047 incompatible headers
  - From: Mutt

Prev by Date: Re: [Mutt] #2883: mutt gets confused when a message disappears from
Next by Date: Re: [Mutt] #3146: bad alignment in help screen
Previous by thread: Re: [Mutt] #3172: mutt-1.5.16: handling of RFC2047 incompatible
Next by thread: [Mutt] #3173: Mutt with gmail crashes after IMAP timeout
Index(es):
- Date
- Thread