| X-IronPort-AV: E=Sophos;i="1.11,500,1111111111"; |
| d="xml'?bin'?scan'12,345,67,89,111,222,333,444,555?rels";a="12345678" |
| From: "Julien Nioche (JIRA)" <jira@apache.org> |
| To: dev@tika.apache.org |
| Subject: [jira] Commented: (TIKA-461) RFC822 messages not parsed |
| Reply-To: dev@tika.apache.org |
| Delivered-To: mailing list dev@tika.apache.org |
| Date: Mon, 6 Sep 2010 05:25:34 -0400 (EDT) |
| In-Reply-To: <6089099.260231278600349994.JavaMail.jira@thor> |
| MIME-Version: 1.0 |
| Content-Type: text/plain; charset=utf-8 |
| Content-Transfer-Encoding: 7bit |
| |
| |
| [ https://issues.apache.org/jira/browse/TIKA-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906468#action_12906468 ] |
| |
| Julien Nioche commented on TIKA-461: |
| ------------------------------------ |
| |
| I'll have a look at mime4j and try to use it in Tika |
| |
| > 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 |
| > |
| > 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. |
| |
