6.0.0-git
2019-03-23

[#2939] Download All Attachments does not include attachments in signed messages
Summary Download All Attachments does not include attachments in signed messages
Queue IMP
Queue Version HEAD
Type Bug
State Resolved
Priority 2. Medium
Owners slusarz (at) horde (dot) org
Requester chuck (at) horde (dot) org
Created 2005-11-08 (4883 days ago)
Due
Updated 2010-01-12 (3357 days ago)
Assigned 2008-11-09 (3786 days ago)
Resolved 2008-12-17 (3748 days ago)
Milestone IMP 5.0
Patch No

History
2008-12-17 05:20:20 Michael Slusarz Comment #9
State ⇒ Resolved
Reply to this comment
This has been fixed in IMP 5.
2008-11-09 01:45:58 Chuck Hagenbuch Comment #8
State ⇒ Assigned
Reply to this comment
Un-stalling for IMP 5.
2005-12-02 00:43:31 Chuck Hagenbuch Comment #7
State ⇒ Stalled
Reply to this comment
Okay, so I'm stalling (essentially resolving) this until such time as 
we have a new MIME lib (assuming IMP 5/Horde 4, though I'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
2005-12-01 22:15:34 Michael Slusarz Comment #6 Reply to this comment
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('2.2') call to the MIME_Contents:: object and it will be 
responsible for rebuilding the data (it sees that 2.2 doesn'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.
2005-12-01 19:17:17 Chuck Hagenbuch Comment #5 Reply to this comment
Michael - I'd like your assessment on whether it'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?
2005-11-13 20:08:33 Michael Slusarz Comment #4
State ⇒ Feedback
Reply to this comment
Unfortunately, this is the same exact issue that prevents us from 
being able to quote signed/encrypted text in replies/forwards.  I'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).
2005-11-08 21:50:49 Chuck Hagenbuch Comment #3
Assigned to Michael Slusarz
State ⇒ Assigned
Reply to this comment
Okay, the file isn't going to attach, so you'll just have to do 
without an example for now. :P
2005-11-08 21:49:09 Chuck Hagenbuch Comment #2 Reply to this comment
Okay, and the file...
2005-11-08 21:44:24 Chuck Hagenbuch Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ Download All Attachments does not include attachments in signed messages
Queue ⇒ IMP
Reply to this comment
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's no 
Add To Gallery option.

Saved Queries