[
https://issues.apache.org/jira/browse/TIKA-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Nioche updated TIKA-461:
-------------------------------
Attachment: TIKA-461.patch
This patch contains an initial version of the RFC822Parser which uses
apache-mime4j
The metadata are currently created only for the main message and not for the
parts. Note that the parts are put inside <p> elements and parsed with the
right parser for their declared mime-type e.g. txt, html etc... The multiparts
seem to be properly handled as well.
There is definitely space for improvements, as usual comments are more than
welcome
> RFC822 messages not parsed
> --------------------------
>
> Key: TIKA-461
> URL: https://issues.apache.org/jira/browse/TIKA-461
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 0.7
> Reporter: Joshua Turner
> Assignee: Julien Nioche
> Attachments: 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.
