6.0.0-git
2019-03-20

[#2759] Decoding MIME
Summary Decoding MIME
Queue Horde Framework Packages
Queue Version HEAD
Type Bug
State Not A Bug
Priority 2. Medium
Owners slusarz (at) horde (dot) org
Requester bocaciua (at) libero (dot) it
Created 2005-10-11 (4908 days ago)
Due
Updated 2005-10-22 (4897 days ago)
Assigned 2005-10-12 (4907 days ago)
Resolved 2005-10-19 (4900 days ago)
Milestone
Patch No

History
2005-10-22 01:38:32 Michael Slusarz Comment #9 Reply to this comment
I'm using the same Mail and Mail_Mime libraries as you - but this 
doesn't make any difference since those libraries would not be used to 
render this message.  Double check to make sure your copies of 
mime_drivers.php in both horde and imp are the same as the .dist files.
2005-10-21 07:35:47 bocaciua (at) libero (dot) it Comment #8 Reply to this comment
ok, but could you at least specify wich version of additional 
libraries are using? maybe is a pear module incompatibility (I'd 
prefer to think php itself as "portable")
2005-10-19 23:20:13 Michael Slusarz Comment #7
State ⇒ Not A Bug
Reply to this comment
Renders fine for me here also.  Since you are the only one 
experiencing this behavior, you will have to track this down yourself.
2005-10-12 10:35:07 bocaciua (at) libero (dot) it Comment #6 Reply to this comment
other packages status:



Mail 1.1.9

Mail_Mime 1.3.1

php-4.4.0-2
2005-10-12 10:30:59 bocaciua (at) libero (dot) it Comment #5
New Attachment: message.tgz Download
Reply to this comment
this is how it is rendered for me in HEAD (as today, 12-10-2005)
2005-10-12 08:20:18 Jan Schneider Comment #4 Reply to this comment
This message is rendered perfectly for me in HEAD.
2005-10-12 07:39:34 bocaciua (at) libero (dot) it Comment #3
New Attachment: Message Source Download
Reply to this comment
this is an example message.
2005-10-12 06:25:41 Michael Slusarz Comment #2
State ⇒ Feedback
Reply to this comment
Please provide a sample message which exhibits the broken behavior.
2005-10-11 20:43:33 Jan Schneider Assigned to Michael Slusarz
State ⇒ Assigned
 
2005-10-11 13:00:39 bocaciua (at) libero (dot) it Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ Decoding MIME
Queue ⇒ Horde Framework Packages
Reply to this comment
bug in framework::mime::structure::parseTextMimeMessage



condition: message/rfc822 incapsulated in other mime parts.



this method should return a mime_message as if decoded from 
imap_fetchstructure but the results differ if there is a nested rfc822 
message.

this prevents the message from being displayed correctly if, for 
example, is contained in a signed S/MIME as the function will rebuild 
the content using the parseTextMIMEMessage.



The incompatibility is raised by this:

the fetchstructure doesn't split up the part of the attached rfc822, 
while the parseTextMIMEMessage does: this way the rfc822 viewer fails 
to parse the messge, as it was expecting a raw text message. Also this 
will prevent the correct download of the rfc822 attachment




Saved Queries