| Summary | unrecognized MIME type mail |
| Queue | IMP |
| Queue Version | 4.1-RC3 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | slusarz (at) horde (dot) org |
| Requester | turpel (at) pt (dot) lu |
| Created | 03/01/2006 (7191 days ago) |
| Due | |
| Updated | 03/02/2006 (7190 days ago) |
| Assigned | 03/01/2006 (7191 days ago) |
| Resolved | 03/01/2006 (7191 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
doesn't matter anyway.
State ⇒ Not A Bug
c-client indicates there is a 'text/plain' (ID:1.3) part after the
multipart/related part (ID:1.2) even though this part doesn't exist in
the source. However, this is a c-client issue since it is
imap_fetchstructure() that is returning the information. Still
strange though.
State ⇒ Assigned
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ unrecognized MIME type mail
Queue ⇒ IMP
New Attachment: badMimeType.mail
will be displayed and the following error message will be logged :
client 194.154.192.249] PHP Fatal error: Call to a member function on
a non-object in
/var/www/html/horde-3.1/framework/MIME/MIME/Contents.php on line 423,
referer: http://horde31-ptweb2.pt.lu/imp/mailbox.php?mailbox=INBOX