Tickets :: [#4554] Content-type becomes broken

6.0.0-beta1

10/16/25

Summary	Content-type becomes broken
Queue	IMP
Queue Version	4.1
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	geshido (at) gmail (dot) com
Created	10/24/2006 (6932 days ago)
Due
Updated	11/05/2006 (6920 days ago)
Assigned	10/24/2006 (6932 days ago)
Resolved	11/03/2006 (6922 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

11/05/2006 01:10:27 PM	geshido (at) gmail (dot) com	Comment #4	Reply to this comment
Definitely either a c-client or PHP cache issue. Yes, thank you guys anyway. It was cache issue.

11/03/2006 07:21:21 AM	Michael Slusarz	Comment #3 State ⇒ Not A Bug	Reply to this comment
Definitely either a c-client or PHP cache issue.

11/03/2006 07:20:53 AM	Michael Slusarz	Deleted Original Message

10/24/2006 10:08:46 AM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
The message works perfectly for me, you probably use a broken c-client version. Try recompiling PHP with a newer c-client library.

10/24/2006 09:27:38 AM	geshido (at) gmail (dot) com	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Content-type becomes broken Queue ⇒ IMP New Attachment: broken-content-type.tgz State ⇒ Unconfirmed	Reply to this comment
Hello guys, I've got the following problem with imp few days ago. When I try to see message with html-part (multipart/alternative), IMP shows me as it is in screenshot attached. As you can see, there is garbage in "multipart" directive of message content type. The source of the message is attached too.