I can't reproduce the other problem either.

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's charset, not the 
server'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->getCharset();



I tried setting the default charset to UTF-8 in Firefox and that 
didn'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.

You can simply fix this by making sure that your server supports 
UTF-8. Decoding should still work if it doesn't though.

Messages with charset UTF-8 and PGP data in the text/plain body don't 
seem to be displayable.



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



"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."



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'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't understand why this happens.



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