| 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 | 10/11/05 (7564 days ago) |
| Due | |
| Updated | 10/22/05 (7553 days ago) |
| Assigned | 10/12/05 (7563 days ago) |
| Resolved | 10/19/05 (7556 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
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.
libraries are using? maybe is a pear module incompatibility (I'd
prefer to think php itself as "portable")
State ⇒ Not A Bug
experiencing this behavior, you will have to track this down yourself.
Mail 1.1.9
Mail_Mime 1.3.1
php-4.4.0-2
New Attachment: message.tgz
New Attachment: Message Source
State ⇒ Feedback
State ⇒ Assigned
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Decoding MIME
Queue ⇒ Horde Framework Packages
State ⇒ Unconfirmed
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