<?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>Forwarded mail with national characters in the subject can be improperly encoded</title> 
  <pubDate>Fri, 10 Apr 2026 19:46:45 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7043</link> 
  <atom:link rel="self" type="application/rss+xml" title="Forwarded mail with national characters in the subject can be improperly encoded" href="https://bugs.horde.org/ticket/7043/rss" /> 
  <description>Forwarded mail with national characters in the subject can be improperly encoded</description> 
 
   
   
  <item> 
   <title>If you forward a mail where the subject includes national ch</title> 
   <description>If you forward a mail where the subject includes national characters when the receiver views the message the &quot;Forwarded Message: [subject]&quot; line can display the &quot;[subject]&quot; incorrectly.  The underlying cause is that the name parameter of the Content-Type header is marked with the wrong charset.  In our case, for example, the text was in UTF-8 but was marked as us-ascii.



Attached is a working patch but I have to admit I don&#039;t really like the solution.  A lot of mail clients (well, Microsoft&#039;s anyway) don&#039;t always handle MIME messages correctly and assume the first character encoding they stumble over is the one that applies for everything in the message.  In this case they will see utf-8 whereas the actual message may have other/another encoding for other MIME parts.</description> 
   <pubDate>Mon, 07 Jul 2008 17:38:15 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7043#t47364</link> 
  </item> 
   
  <item> 
   <title>I&#039;m not sure I understood the issue correctly. Can you uploa</title> 
   <description>I&#039;m not sure I understood the issue correctly. Can you upload a message that is incorrectly forwarded? Which forwarding method do you use? And which is your default charset for sending messages?</description> 
   <pubDate>Wed, 09 Jul 2008 10:41:06 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7043#t47398</link> 
  </item> 
   
  <item> 
   <title>jnnnnnnnnnnnklmk;kl;mlm;lmkkkkkkkkkkkkkkkkkkklnnjkn</title> 
   <description>jnnnnnnnnnnnklmk;kl;mlm;lmkkkkkkkkkkkkkkkkkkklnnjkn</description> 
   <pubDate>Sun, 13 Jul 2008 13:07:14 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7043#t47498</link> 
  </item> 
   
  <item> 
   <title>Sorry about that.  Should have added more complete informati</title> 
   <description>Sorry about that.  Should have added more complete information and a scenario.  The scenario is:



User A sends a mail to User B where the subject of the mail includes national characters, in this case Swedish characters.  The encoding selected before sending the mail is iso-8859-1.  



User B opens the mail, selects &quot;Forward Entire Message&quot;, and chooses to send the mail with the original message as an inline attachment.  B also selects iso-8859-1 as the encoding and sends it to User C.



When C opens the mail, the subject is fine but in the &quot;parts&quot; listing you&#039;ll see &quot;Forwarded Message: &lt;original_subject&gt;&quot; where &lt;original_subject&gt; is the subject but where the UTF-8 characters are displayed literally for the national characters.  



Attached is forwarded_message.jpg which makes it a lot clearer (&lt;original_subject&gt; is circled in the image).  I&#039;ve also attached the MIME message.



As you see in the MIME message, the &quot;name&quot; parameter of the message/rfc822 Content-Type header is marked as being encoded in us-ascii, but because we are running everything to output UTF-8 the actual text string set on the name parameter is UTF-8 encoded.  Not sure our web output encoding is really important since when the message/rfc822 MIME_Part is created no encoding was being set so it defaulted to us-ascii as it should, but this affected the value of the name parameter of the Content-Type header where the code assumes it is already in whatever character set that applies to the part.  

</description> 
   <pubDate>Mon, 14 Jul 2008 07:34:28 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7043#t47506</link> 
  </item> 
   
  <item> 
   <title>Wasn&#039;t this already fixed by this change from a month ago?

</title> 
   <description>Wasn&#039;t this already fixed by this change from a month ago?

http://cvs.horde.org/diff.php/imp/lib/Compose.php?r1=1.365&amp;r2=1.366</description> 
   <pubDate>Tue, 15 Jul 2008 05:07:32 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7043#t47528</link> 
  </item> 
   
  <item> 
   <title>Completely missed that one.  Case closed.  Sorry for the tro</title> 
   <description>Completely missed that one.  Case closed.  Sorry for the trouble.</description> 
   <pubDate>Tue, 15 Jul 2008 07:29:10 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7043#t47535</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
