Re: [Mutt] #1430: Inline PGP messages -> special characters shown as question marks

To: dunkelkammer@xxxxxx, rodrigob@xxxxxxxxxxxxxxx, roessler@xxxxxxxxxxxxxxxxxx, pdmef@xxxxxxx
Subject: Re: [Mutt] #1430: Inline PGP messages -> special characters shown as question marks
From: Mutt <fleas@xxxxxxxx>
Date: Sat, 06 Jun 2009 22:08:25 -0000
Auto-submitted: auto-generated
Cc: mutt-dev@xxxxxxxx
In-reply-to: <067.5dbc5004ae46ba65f0f4fd4dcad1b62c@xxxxxxxx>
Mail-followup-to: fleas@xxxxxxxx
References: <067.5dbc5004ae46ba65f0f4fd4dcad1b62c@xxxxxxxx>
Reply-to: fleas@xxxxxxxx
#1430: Inline PGP messages -> special characters shown as question marks
--------------------------------------------------+-------------------------
  Reporter:  Stefan Walter <dunkelkammer@xxxxxx>  |       Owner:  mutt-dev
      Type:  defect                               |      Status:  closed  
  Priority:  minor                                |   Milestone:          
 Component:  mutt                                 |     Version:  1.5.1i  
Resolution:  fixed                                |    Keywords:          
--------------------------------------------------+-------------------------
Changes (by pdmef):

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


Old description:

> {{{
> Package: mutt
> Version: 1.5.1i
> Severity: normal
>
> -- Please type your report below this line
> Since the update from mutt 1.3.x to version 1.5.1, special characters
> like German umlauts are displayed as question marks when used in
> inline/traditional PGP messages (created with Windows clients such as
> The Bat! and Pegasus Mail). This happens at the console as well as in a
> (x|w)term, and my settings for these haven't changed for quite a while.
> PGP/MIME doesn't seem to be a problem (though I don't have many contacts
> to test it with), and gpg decrypts all messages properly when invoked on
> a message saved to a file or by piping the message to it from mutt.
>
> I can create inline PGP messages myself, of course, and those are
> displayed correctly with me, but not with the recipients (again, Windows
> clients).
>
> This problem has been posted to the comp.mail.mutt newsgroup before as
> well (message-id: 2uphta.f07.ln@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx), but
> neither a working solution nor someone else with the same problem has
> been found so far.
>
> Excerpt from my configuration (note that gpg is invoked with 'utf-8' as
> its charset here, but the problem persists if I change the parameter to
> 'iso-8859-1'):
>
> ***
> set charset="iso-8859-1"
>
> # decode application/pgp
> set pgp_decode_command="/usr/local/bin/gpg --charset utf-8 %?p
> ?--passphrase-fd 0? --no-verbose --quiet --batch --output - %f"
>
> # verify a pgp/mime signature
> set pgp_verify_command="/usr/local/bin/gpg --no-verbose --quiet --batch
> --output - --verify %s %f"
>
> # decrypt a pgp/mime attachment
> set pgp_decrypt_command="/usr/local/bin/gpg --passphrase-fd 0 --no-
> verbose --quiet --batch  --output - %f"
>
> # create a pgp/mime signed attachment
> set pgp_sign_command="/usr/local/bin/gpg    --no-verbose --batch --quiet
> --output -  --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a?
> %f"
>
> # create a application/pgp signed (old-style) message
> set pgp_clearsign_command="/usr/local/bin/gpg --charset utf-8 --no-
> verbose --batch --quiet  --output - --passphrase-fd 0 --armor --textmode
> --clearsign %?a?-u %a? %f"
>
> # create a pgp/mime encrypted attachment
> set pgp_encrypt_only_command="pgpewrap /usr/local/bin/gpg --charset utf-8
> --batch --quiet  --no-verbose --output - --encrypt --textmode --armor
> --always-trust -- -r %r -- %f"
>
> # create a pgp/mime encrypted and signed attachment
> set pgp_encrypt_sign_command="pgpewrap /usr/local/bin/gpg --charset utf-8
> --passphrase-fd  0 --batch --quiet --no-verbose --textmode --output -
> --encrypt --sign %?a?-u %a? --armor    --always-trust -- -r %r -- %f"
> ***
>
> -- 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
> cc -I/usr/local/include
> Using builtin specs.
> gcc version 2.95.4 20020320 [FreeBSD]
>
> - CFLAGS
> -Wall -O -pipe
>
> -- Mutt Version Information
>
> Mutt 1.5.1i (2002-05-02)
> Copyright (C) 1996-2001 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: FreeBSD 4.7-STABLE (i386) [using slang 10405] [using libiconv
> 1.8]
> Compile options:
> -DOMAIN
> -DEBUG
> -HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE
> -USE_FCNTL  +USE_FLOCK
> +USE_POP  +USE_IMAP  -USE_GSS  +USE_SSL  -USE_SASL
> +HAVE_REGCOMP  -USE_GNU_REGEX
> +HAVE_COLOR  -HAVE_START_COLOR  -HAVE_TYPEAHEAD  -HAVE_BKGDSET
> -HAVE_CURS_SET  -HAVE_META  -HAVE_RESIZETERM
> +HAVE_PGP  +HAVE_SMIME  -BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT
> +ENABLE_NLS  -LOCALES_HACK  -HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET
> +HAVE_LANGINFO_YESEXPR
> +HAVE_ICONV  -ICONV_NONTRANS  +HAVE_GETSID  +HAVE_GETADDRINFO
> -ISPELL
> SENDMAIL="/usr/sbin/sendmail"
> MAILPATH="/var/mail"
> PKGDATADIR="/usr/local/share/mutt"
> SYSCONFDIR="/usr/local/etc"
> EXECSHELL="/bin/sh"
> -MIXMASTER
> To contact the developers, please mail to <mutt-dev@xxxxxxxx>.
> To report a bug, please use the flea(1) utility.
>
> %s%sco %sco -l %srcsdiff %s > /dev/nullRCSs.SCCS/%s%sget %sget -e %sget
> -p %s | diff - %s >/dev/nullSCCScan't find %s
> patch-1.5.1.cd.signatures_menu.2.1
>

> >How-To-Repeat:
>
> >Fix:
> }}}

New description:

 {{{
 Package: mutt
 Version: 1.5.1i
 Severity: normal

 -- Please type your report below this line
 Since the update from mutt 1.3.x to version 1.5.1, special characters
 like German umlauts are displayed as question marks when used in
 inline/traditional PGP messages (created with Windows clients such as
 The Bat! and Pegasus Mail). This happens at the console as well as in a
 (x|w)term, and my settings for these haven't changed for quite a while.
 PGP/MIME doesn't seem to be a problem (though I don't have many contacts
 to test it with), and gpg decrypts all messages properly when invoked on
 a message saved to a file or by piping the message to it from mutt.

 I can create inline PGP messages myself, of course, and those are
 displayed correctly with me, but not with the recipients (again, Windows
 clients).

 This problem has been posted to the comp.mail.mutt newsgroup before as
 well (message-id: 2uphta.f07.ln@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx), but
 neither a working solution nor someone else with the same problem has
 been found so far.

 Excerpt from my configuration (note that gpg is invoked with 'utf-8' as
 its charset here, but the problem persists if I change the parameter to
 'iso-8859-1'):

 ***
 set charset="iso-8859-1"

 # decode application/pgp
 set pgp_decode_command="/usr/local/bin/gpg --charset utf-8 %?p
 ?--passphrase-fd 0? --no-verbose --quiet --batch --output - %f"

 # verify a pgp/mime signature
 set pgp_verify_command="/usr/local/bin/gpg --no-verbose --quiet --batch
 --output - --verify %s %f"

 # decrypt a pgp/mime attachment
 set pgp_decrypt_command="/usr/local/bin/gpg --passphrase-fd 0 --no-verbose
 --quiet --batch  --output - %f"

 # create a pgp/mime signed attachment
 set pgp_sign_command="/usr/local/bin/gpg    --no-verbose --batch --quiet
 --output -  --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a?
 %f"

 # create a application/pgp signed (old-style) message
 set pgp_clearsign_command="/usr/local/bin/gpg --charset utf-8 --no-verbose
 --batch --quiet  --output - --passphrase-fd 0 --armor --textmode
 --clearsign %?a?-u %a? %f"

 # create a pgp/mime encrypted attachment
 set pgp_encrypt_only_command="pgpewrap /usr/local/bin/gpg --charset utf-8
 --batch --quiet  --no-verbose --output - --encrypt --textmode --armor
 --always-trust -- -r %r -- %f"

 # create a pgp/mime encrypted and signed attachment
 set pgp_encrypt_sign_command="pgpewrap /usr/local/bin/gpg --charset utf-8
 --passphrase-fd  0 --batch --quiet --no-verbose --textmode --output -
 --encrypt --sign %?a?-u %a? --armor    --always-trust -- -r %r -- %f"
 ***

 -- 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
 cc -I/usr/local/include
 Using builtin specs.
 gcc version 2.95.4 20020320 [FreeBSD]

 - CFLAGS
 -Wall -O -pipe

 -- Mutt Version Information

 Mutt 1.5.1i (2002-05-02)
 Copyright (C) 1996-2001 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: FreeBSD 4.7-STABLE (i386) [using slang 10405] [using libiconv 1.8]
 Compile options:
 -DOMAIN
 -DEBUG
 -HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE
 -USE_FCNTL  +USE_FLOCK
 +USE_POP  +USE_IMAP  -USE_GSS  +USE_SSL  -USE_SASL
 +HAVE_REGCOMP  -USE_GNU_REGEX
 +HAVE_COLOR  -HAVE_START_COLOR  -HAVE_TYPEAHEAD  -HAVE_BKGDSET
 -HAVE_CURS_SET  -HAVE_META  -HAVE_RESIZETERM
 +HAVE_PGP  +HAVE_SMIME  -BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT
 +ENABLE_NLS  -LOCALES_HACK  -HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET
 +HAVE_LANGINFO_YESEXPR
 +HAVE_ICONV  -ICONV_NONTRANS  +HAVE_GETSID  +HAVE_GETADDRINFO
 -ISPELL
 SENDMAIL="/usr/sbin/sendmail"
 MAILPATH="/var/mail"
 PKGDATADIR="/usr/local/share/mutt"
 SYSCONFDIR="/usr/local/etc"
 EXECSHELL="/bin/sh"
 -MIXMASTER
 To contact the developers, please mail to <mutt-dev@xxxxxxxx>.
 To report a bug, please use the flea(1) utility.

 %s%sco %sco -l %srcsdiff %s > /dev/nullRCSs.SCCS/%s%sget %sget -e %sget -p
 %s | diff - %s >/dev/nullSCCScan't find %s
 patch-1.5.1.cd.signatures_menu.2.1


 >How-To-Repeat:

 >Fix:
 }}}

--

Comment:

 If this isn't solved by changeset [7d44a83efcc6] supporting the Charset:
 armor header for inline pgp, I'm afraid mutt can't do anything except
 assuming UTF-8 as pointed out already.

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/1430#comment:6>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Prev by Date: Re: [Mutt] #2995: Mutt is folding subject line folds using a tab,
Next by Date: Re: [Mutt] #2248: Mutt could be smarter with QP-encoded newlines
Previous by thread: Re: Brightness bug and possible fix
Next by thread: Re: [Mutt] #2248: Mutt could be smarter with QP-encoded newlines
Index(es):
- Date
- Thread