<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>PGP problem with charset UTF-8</title> 
  <pubDate>Fri, 10 Apr 2026 06:14:13 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7218</link> 
  <atom:link rel="self" type="application/rss+xml" title="PGP problem with charset UTF-8" href="https://bugs.horde.org/ticket/7218/rss" /> 
  <description>PGP problem with charset UTF-8</description> 
 
   
   
  <item> 
   <title>Messages with charset UTF-8 and PGP data in the text/plain b</title> 
   <description>Messages with charset UTF-8 and PGP data in the text/plain body don&#039;t seem to be displayable.



When such a message is clicked on, instead of the PGP passphrase prompt, we see this message:



&quot;This message was written in a character set (UTF-8) other than your own. If it is not displayed correctly, click here to open it in a new window.&quot;



It works fine if the charset is US-ASCII.



I tried editing the mail files on the IMAP server and changing the Content-type header, but that didn&#039;t seem to make any difference within IMP. Clicking Message Source shows the edited message with the new Content-type header, but IMP continues to emit the above message about UTF-8 charset. I don&#039;t understand why this happens.



Clicking on the link in the message doesn&#039;t start the decryption process for the message, but simply shows the encrypted message in a new window.

</description> 
   <pubDate>Mon, 18 Aug 2008 20:52:27 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7218#t48283</link> 
  </item> 
   
  <item> 
   <title>You can simply fix this by making sure that your server supp</title> 
   <description>You can simply fix this by making sure that your server supports UTF-8. Decoding should still work if it doesn&#039;t though.</description> 
   <pubDate>Mon, 18 Aug 2008 22:43:06 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7218#t48293</link> 
  </item> 
   
  <item> 
   <title>&gt; You can simply fix this by making sure that your server su</title> 
   <description>&gt; You can simply fix this by making sure that your server supports 

&gt; UTF-8. Decoding should still work if it doesn&#039;t though.



How do I make sure Apache 1.3.29 supports UTF-8? 



I tried AddDefaultCharset UTF-8 in the relevant VirtualHost section and it made no difference.



The comments in the code at the relevant point in lib/Horde/MIME/Contents.php refer to the browser&#039;s charset, not the server&#039;s:



        /* If this is a text/* part, AND the text is in a different character

         * set than the browser, convert to the current character set.

         * Additionally, if the browser does not support UTF-8, give the

         * user a link to open the part in a new window with the correct

         * character set. */

        $charset = $mime_part-&gt;getCharset();



I tried setting the default charset to UTF-8 in Firefox and that didn&#039;t make any difference either.



As of now, PGP messages coming in as text/plain parts with charset UTF-8 fail to trigger PGP decryption and only show this charset message.</description> 
   <pubDate>Tue, 19 Aug 2008 06:01:04 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7218#t48297</link> 
  </item> 
   
  <item> 
   <title>I can&#039;t reproduce the other problem either.</title> 
   <description>I can&#039;t reproduce the other problem either.</description> 
   <pubDate>Mon, 22 Sep 2008 15:24:56 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7218#t49120</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
