<?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>Download All Attachments does not include attachments in signed messages</title> 
  <pubDate>Fri, 10 Apr 2026 19:06:55 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/2939</link> 
  <atom:link rel="self" type="application/rss+xml" title="Download All Attachments does not include attachments in signed messages" href="https://bugs.horde.org/ticket/2939/rss" /> 
  <description>Download All Attachments does not include attachments in signed messages</description> 
 
   
   
  <item> 
   <title>Instead, I get just the signature file. Attached is a (zippe</title> 
   <description>Instead, I get just the signature file. Attached is a (zipped, large) message that demonstrates the problem. Also, not sure if it should or not, but in the inlined attachment listings for the images, there&#039;s no Add To Gallery option.</description> 
   <pubDate>Tue, 08 Nov 2005 21:44:24 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2939#t13539</link> 
  </item> 
   
  <item> 
   <title>Okay, and the file...</title> 
   <description>Okay, and the file...</description> 
   <pubDate>Tue, 08 Nov 2005 21:49:09 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2939#t13540</link> 
  </item> 
   
  <item> 
   <title>Okay, the file isn&#039;t going to attach, so you&#039;ll just have to</title> 
   <description>Okay, the file isn&#039;t going to attach, so you&#039;ll just have to do without an example for now. :P</description> 
   <pubDate>Tue, 08 Nov 2005 21:50:49 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2939#t13541</link> 
  </item> 
   
  <item> 
   <title>Unfortunately, this is the same exact issue that prevents us</title> 
   <description>Unfortunately, this is the same exact issue that prevents us from being able to quote signed/encrypted text in replies/forwards.  I&#039;m not sure how much we can do without terribly breaking BC (or, at the least, rewriting MIME_Contents:: in IMP just to work around BC issues).</description> 
   <pubDate>Sun, 13 Nov 2005 20:08:33 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2939#t13657</link> 
  </item> 
   
  <item> 
   <title>Michael - I&#039;d like your assessment on whether it&#039;s worth inc</title> 
   <description>Michael - I&#039;d like your assessment on whether it&#039;s worth including a revamped MIME_Contents package in IMP that can handle this sort of thing, or if this ticket should be closed as undoable?</description> 
   <pubDate>Thu, 01 Dec 2005 19:17:17 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2939#t14396</link> 
  </item> 
   
  <item> 
   <title>What I would eventually like is to refer to these embedded m</title> 
   <description>What I would eventually like is to refer to these embedded mime parts by an id.  PGP Example:

0. multipart/signed

  1. encryption signature/version stuff

  2. encryped data

    Encrypted data contains:

    1. multipart/mixed

      1. text/plain

      2. image/jpeg



Then, if we want to access the image/jpeg option, we do a getPart(&#039;2.2&#039;) call to the MIME_Contents:: object and it will be responsible for rebuilding the data (it sees that 2.2 doesn&#039;t exist on the IMAP server, but that id 2 can contain embedded data, so it automatically downloads/parses as many parent parts as required).  This will eliminate the need for MIME specific caching - which was always kind of a hackish implementation by me I admit.  But, alas, I think this will require enough changes that it is just not worth it to do the coding gymnastics necessary to cram everything into IMP for purposes maintaining BC.</description> 
   <pubDate>Thu, 01 Dec 2005 22:15:34 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2939#t14403</link> 
  </item> 
   
  <item> 
   <title>Okay, so I&#039;m stalling (essentially resolving) this until suc</title> 
   <description>Okay, so I&#039;m stalling (essentially resolving) this until such time as we have a new MIME lib (assuming IMP 5/Horde 4, though I&#039;d really like to see it possible to bundle an updated whole MIME package with an IMP 4 version instead, but your call), and have added notes to the wiki on what a new MIME lib should have, quoting you:



http://wiki.horde.org/NewMIMELib</description> 
   <pubDate>Fri, 02 Dec 2005 00:43:31 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2939#t14454</link> 
  </item> 
   
  <item> 
   <title>Un-stalling for IMP 5.</title> 
   <description>Un-stalling for IMP 5.</description> 
   <pubDate>Sun, 09 Nov 2008 01:45:58 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2939#t50498</link> 
  </item> 
   
  <item> 
   <title>This has been fixed in IMP 5.</title> 
   <description>This has been fixed in IMP 5.</description> 
   <pubDate>Wed, 17 Dec 2008 05:20:20 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2939#t51308</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git for this ticket:

Mark Bug #29</title> 
   <description>Changes have been made in Git for this ticket:

Mark Bug #2939 as complete.

http://git.horde.org/diff.php/imp/docs/CHANGES?rt=horde-git&amp;r1=880d5e5cb57efcff5376c3fcbd81c32d3c75e169&amp;r2=4b75c91ba3c108bf447725e207daa7c8217aebb0</description> 
   <pubDate>Tue, 12 Jan 2010 23:55:56 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2939#t57482</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
