[
https://issues.apache.org/jira/browse/TIKA-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Douglas updated TIKA-461:
----------------------------------
Attachment: TIKA-461-parse.patch
Thank you for committing the changes up to now.
I am attaching an attempt at wiring up the mime4j parsers into the
MailContentHandler. All of the unit tests now pass, with mime4j parsing quoted
printable, base64, and i18n encoded text. I needed to re-submit the test files
and mark them as binary, since svn was clobbering the CRLF line breaks that are
part of the RFC822 format. Please take a look.
I have not touched anything in the area of the refactoring mentioned above.
> RFC822 messages not parsed
> --------------------------
>
> Key: TIKA-461
> URL: https://issues.apache.org/jira/browse/TIKA-461
> Project: Tika
> Issue Type: New Feature
> Components: parser
> Affects Versions: 0.7
> Reporter: Joshua Turner
> Assignee: Julien Nioche
> Attachments: testRFC822-multipart, TIKA-461-parse.patch,
> TIKA-461-plus-tests-1.patch, TIKA-461.patch
>
>
> Presented with an RFC822 message exported from Thunderbird, AutodetectParser
> produces an empty body, and a Metadata containing only one key-value pair:
> "Content-Type=message/rfc822". Directly calling MboxParser likewise gives an
> empty body, but with two metadata pairs: "Content-Encoding=us-ascii
> Content-Type=application/mbox".
> A quick peek at the source of MboxParser shows that the implementation is
> pretty naive. If the wiring can be sorted out, something like Apache James'
> mime4j might be a better bet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
