tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir L. (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-879) Detection problem: message/rfc822 file is detected as text/plain.
Date Wed, 21 Nov 2012 20:32:00 GMT

    [ https://issues.apache.org/jira/browse/TIKA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502287#comment-13502287

Vladimir L. commented on TIKA-879:

I've got the same problem: trying to parse Outlook Express file: *.eml and get default "text/plain"
Content-Type instead of expected "message/rfc822"

I'm using <pre>org.apache.tika.parser.AutoDetectParser</pre> with default settings
and during debugging came to the same conclusion as a reporter of this issue: "MediaTypeRegistry.isSpecializationOf("message/rfc822",
"text/plain") returns false".

If there is a way to vote for this bug to be fixed, or easy work around, please share it with
> Detection problem: message/rfc822 file is detected as text/plain.
> -----------------------------------------------------------------
>                 Key: TIKA-879
>                 URL: https://issues.apache.org/jira/browse/TIKA-879
>             Project: Tika
>          Issue Type: Bug
>          Components: metadata, mime
>    Affects Versions: 1.0, 1.1, 1.2
>         Environment: linux 3.2.9
> oracle jdk7, openjdk7, sun jdk6
>            Reporter: Konstantin Gribov
> When using {{DefaultDetector}} mime type for {{.eml}} files is different (you can test
it on {{testRFC822}} and {{testRFC822_base64}} in {{tika-parsers/src/test/resources/test-documents/}}).
> Main reason for such behavior is that only magic detector is really works for such files.
Even if you set {{CONTENT_TYPE}} in metadata or some {{.eml}} file name in {{RESOURCE_NAME_KEY}}.
> As I found {{MediaTypeRegistry.isSpecializationOf("message/rfc822", "text/plain")}} returns
{{false}}, so detection by {{MimeTypes.detect(...)}} works only by magic.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message