Skip Menu |

This queue is for tickets about the Mail-Mbox-MessageParser CPAN distribution.

Report information
The Basics
Id: 19817
Status: stalled
Priority: 0/
Queue: Mail-Mbox-MessageParser

People
Owner: Nobody in particular
Requestors: pmiscml [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.4003
Fixed in: (no value)



Subject: Wrong assumption parsing Multipart/Mixed messages
Hello, We (sourceforge.net) use Mail-Mbox-MessageParser to parse Mailman mailboxes for frontend presentation. Recently had an issue when parser stumbled on one messages, ingoring mailbox content after it. Traced this to following: a message has Content-Type: Multipart/Mixed;, but actually doesn't have any MIME parts,only plain text content. But Mail- Mbox-MessageParser, once seeing myltipart messages, tries to search for *end* boundary within a mailbox - without bothering to check, if there was a beginning. So, it just slurps mailbox till the end and reports EOF. Our current fix is to disable multipart processing at all - after all, probability of fully well-formed "From " line in attachment is low, and ieven if it is, we hope that parser will recover from, while current situation of dead end is really bad. Hope that more correct fix will be implemented... Regards, Paul Sokolovsky, http://sourceforge.net/users/pfalcon SourceForge developer http://sourceforge.net
On Sat Jun 10 13:48:16 2006, guest wrote: Show quoted text
> Traced > this to following: a message has Content-Type: Multipart/Mixed;, but > actually doesn't have any MIME parts,only plain text content. But Mail- > Mbox-MessageParser, once seeing myltipart messages, tries to search > for *end* boundary within a mailbox - without bothering to check, if > there was a beginning. So, it just slurps mailbox till the end and > reports EOF.
Can you provide me with a sample mailbox? All I need is just the offending email and perhaps the one right after it. You can anonymize the mailbox using the utility provided in the distribution.