6.0.0-beta1
7/26/25

[#3550] unrecognized MIME type mail
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 (7087 days ago)
Due
Updated 03/02/2006 (7086 days ago)
Assigned 03/01/2006 (7087 days ago)
Resolved 03/01/2006 (7087 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
03/02/2006 10:18:47 AM Jan Schneider Comment #3 Reply to this comment
This was actually FW3 code, not RC3. But if it's a c-client issue, it 
doesn't matter anyway.
03/01/2006 05:41:15 PM Michael Slusarz Comment #2
State ⇒ Not A Bug
Reply to this comment
Works with latest F_3 code.  Although, strangely enough, my version of 
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.
03/01/2006 05:20:10 PM Jan Schneider Assigned to Michael Slusarz
State ⇒ Assigned
 
03/01/2006 02:14:03 PM turpel (at) pt (dot) lu Comment #1
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ unrecognized MIME type mail
Queue ⇒ IMP
New Attachment: badMimeType.mail Download
Reply to this comment
When selecting the attached mail in your Inbox a blank (empty) frame 
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


Saved Queries