[
https://issues.apache.org/jira/browse/NIFI-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andre updated NIFI-2380:
------------------------
Description:
during the review of NIFI-1899 Dan Marshall highlighted some use cases for
email processing that have not been addressed as part of the initial
development cycle.
One of these use cases was the decoding of Microsoft Transport Neutral Encoding
Files (TNEF).
This type of attachments is popularly know as winmail.dat and uses a non RFC
compliant structure to transfer attachments across different Microsoft Outlook
clients.
Given the prevalence of outlook and the issues with winmail.dat files, it would
be nice to be able to decode TNEF as we currently do with MIME attachments.
Permalink to Dan's comments
http://mail-archives.apache.org/mod_mbox/nifi-dev/201607.mbox/%3C1468716836729-12827.post%40n7.nabble.com%3E
was:
during the review of NIFI-1899 Dan Marshall highlighted some use cases for
email processing that have not been addressed as part of the initial
development cycle.
One of these use cases was the decoding of Microsoft Transport Neutral Encoding
Files (TNEF).
This type of attachments is popularly know as winmail.dat and uses a non RFC
compliant structure to transfer attachments across different Microsoft Outlook
clients.
Given the prevalence of outlook and the issues with winmail.dat files, it would
be nice to be able to decode TNEF as we currently do with MIME attachments.
> ExtractEmailAttachments processor should support TNEF files (aka winmail.dat)
> -----------------------------------------------------------------------------
>
> Key: NIFI-2380
> URL: https://issues.apache.org/jira/browse/NIFI-2380
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.0.0
> Reporter: Andre
>
> during the review of NIFI-1899 Dan Marshall highlighted some use cases for
> email processing that have not been addressed as part of the initial
> development cycle.
> One of these use cases was the decoding of Microsoft Transport Neutral
> Encoding Files (TNEF).
> This type of attachments is popularly know as winmail.dat and uses a non RFC
> compliant structure to transfer attachments across different Microsoft
> Outlook clients.
> Given the prevalence of outlook and the issues with winmail.dat files, it
> would be nice to be able to decode TNEF as we currently do with MIME
> attachments.
> Permalink to Dan's comments
> http://mail-archives.apache.org/mod_mbox/nifi-dev/201607.mbox/%3C1468716836729-12827.post%40n7.nabble.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
