<?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>Problem with signed messages</title> 
  <pubDate>Fri, 10 Apr 2026 09:50:11 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7048</link> 
  <atom:link rel="self" type="application/rss+xml" title="Problem with signed messages" href="https://bugs.horde.org/ticket/7048/rss" /> 
  <description>Problem with signed messages</description> 
 
   
   
  <item> 
   <title>A signed mail containing as attachment a signed message is n</title> 
   <description>A signed mail containing as attachment a signed message is not visualized at all.

In particular, the attacched message appears to be empty.

The same mail, viewed with every else clients we tested as squirrel, OE, etc., is correctly displayed.</description> 
   <pubDate>Tue, 08 Jul 2008 11:30:25 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7048#t47385</link> 
  </item> 
   
  <item> 
   <title>Duplicate of 1866.</title> 
   <description>Duplicate of 1866.</description> 
   <pubDate>Tue, 08 Jul 2008 18:36:07 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7048#t47394</link> 
  </item> 
   
  <item> 
   <title>I don&#039;t recognize 1866 as an answer or a solution. 

The pro</title> 
   <description>I don&#039;t recognize 1866 as an answer or a solution. 

The problem i noticed has two aspects.

The first is surely mime objects treatment but i believe tha demime functions don&#039;t work correctly because (second aspect) the object (in my own case a digitally signed message) is corrupted in a some way. In fact, if i try to redirect the message to another account (or saving it on desktop) and to view it using another client (i.e. OE) the signature is not recognized at all and message is notified as corrupted (in both cases). If the same message is directly sent to an account managed by a different client, it is correctly displayed.

The, i argue that is not only a visualization problem but a decoding failure. </description> 
   <pubDate>Wed, 09 Jul 2008 10:29:50 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7048#t47397</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
