tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Allison (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TIKA-2455) Flag in metadata for alternative email bodies
Date Tue, 24 Oct 2017 00:40:00 GMT

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

Tim Allison resolved TIKA-2455.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.17

Thank you, [~mcaruanagalizia]!

> Flag in metadata for alternative email bodies
> ---------------------------------------------
>
>                 Key: TIKA-2455
>                 URL: https://issues.apache.org/jira/browse/TIKA-2455
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 1.16
>            Reporter: Matthew Caruana Galizia
>            Priority: Minor
>              Labels: attachments, multipart, rfc822, rfc822parser
>             Fix For: 1.17
>
>
> When multipart RFC822 emails are being parsed, there's no way to distinguish between
alternative versions of the body and attachments.
> It would be ideal if some kind of flag were set in the metadata passed to the {{EmbeddedDocumentExtractor}}
that indicates that the stream is an alternative.
> In GUIs that present the data extracted from the email, alternative bodies can be distinguished
from attachments and presented separately.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message