Tickets :: [#3757] Unsupported multipart/report message

6.0.0-beta1

9/24/25

Summary	Unsupported multipart/report message
Queue	IMP
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	1. Low
Owners	slusarz (at) horde (dot) org
Requester	jan (at) horde (dot) org
Created	04/11/2006 (7106 days ago)
Due
Updated	04/13/2006 (7104 days ago)
Assigned	04/11/2006 (7106 days ago)
Resolved	04/13/2006 (7104 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

04/13/2006 05:04:16 AM	Michael Slusarz	Comment #4 State ⇒ Resolved	Reply to this comment
That message is broken (it has only 2 parts - the RFC requires 3). I've made a change to display the entire text of the report message. There really is no BC way to show either a link to an individual part or all parts in this kind of setting. Also, showing the first part may not be terribly useful either. Thus, the compromise I coded.

04/11/2006 03:44:58 PM	Jan Schneider	Comment #3 New Attachment: ERR_ Brute force attack.eml	Reply to this comment
Ehm...

04/11/2006 03:21:12 PM	Michael Slusarz	Comment #2	Reply to this comment
What message? :)

04/11/2006 10:58:55 AM	Jan Schneider	Comment #1 State ⇒ Assigned Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Unsupported multipart/report message Queue ⇒ IMP Assigned to Michael Slusarz	Reply to this comment
I'm not sure if this message is broken, but at least the report mime viewer was not able to handle it. It even told me that, but only displayed the message headers. I think it should fall back to show either the first body part or provide links to the different parts.