tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TIKA-461) RFC822 messages not parsed
Date Wed, 13 Apr 2011 17:44:05 GMT

     [ https://issues.apache.org/jira/browse/TIKA-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting resolved TIKA-461.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0

I committed the pending patches in revisions 1091859 and 1091860. Resolving as fixed.

> 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
>             Fix For: 1.0
>
>         Attachments: TIKA-461-config.patch, TIKA-461-parse.patch, TIKA-461-plus-tests-1.patch,
TIKA-461.patch, extra_metadata.patch, testRFC822-CC-BCC, testRFC822-big, testRFC822-multipart
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message