[
https://issues.apache.org/jira/browse/TIKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364657#comment-17364657
]
Luís Filipe Nassif edited comment on TIKA-3445 at 6/17/21, 3:22 AM:
--------------------------------------------------------------------
Maybe apache mime4j (or other library) can handle this message fine with non
strict parsing on. This could be an issue with strict parsing of Aspose
library, instead. The sample looks like an eml message to me too. What RFC822
say about headers, are they needed for valid emails? (but we know there are
lots of non compliant files of different formats around with relevant info that
ideally should be identified and handled using best effort approaches...)
was (Author: lfcnassif):
Maybe apache mime4j (or other library) can handle this message fine with non
strict parsing on. This could be an issue with strict parsing of Aspose
library, instead. The sample looks like an eml message to me too. What RFC822
say about headers, are they needed for valid emails?
> Extension reading it as eml instead of txt when headers are not present
> -----------------------------------------------------------------------
>
> Key: TIKA-3445
> URL: https://issues.apache.org/jira/browse/TIKA-3445
> Project: Tika
> Issue Type: Bug
> Components: core, detector, metadata, mime, parser
> Affects Versions: 1.25, 1.26
> Reporter: Vamsi Molli
> Priority: Blocker
> Fix For: 1.24.1
>
> Attachments: test_sample_message (1).txt
>
>
> The attached txt file doesn't have starting headers it is treating as .eml
> file but it should be .txt.
> stream = TikaInputStream.get(fis = new FileInputStream(paths));stream =
> TikaInputStream.get(fis = new FileInputStream(paths));
> metadata.add(Metadata.RESOURCE_NAME_KEY, paths); MediaType mediaType =
> detector.detect(stream, metadata);
> MediaType detect(InputStream input, Metadata metadata) throws IOException;
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
