[
https://issues.apache.org/jira/browse/TIKA-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965154#action_12965154
]
Benjamin Douglas commented on TIKA-461:
---------------------------------------
Following a discussion with Julien, I am attaching an additional patch with
some tests. I created the content mostly by hand, but took the various features
(quoted-printable encoding, non-ASCII character sets) from the public domain
email collection I have (Enron data set). The tests mostly fail at the moment,
as it seems that the full feature-set of mime4j has not been wired up yet,
though a cursory look through the docs leads me to believe everything should be
possible using mime4j.
As this set only includes plain text, single part documents, I will work on
creating tests for html and multi-part messages next.
> 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: 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.
