[
https://issues.apache.org/jira/browse/NIFI-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15515789#comment-15515789
]
Andre commented on NIFI-2709:
-----------------------------
[~ozhurakousky]
I am not sure what the Spring approach but commons mail seems to address this
compatibility issue:
https://commons.apache.org/proper/commons-net/apidocs/org/apache/commons/net/imap/IMAPClient.FETCH_ITEM_NAMES.html
> Email processors with Exchange don't output to RFC2822 format
> -------------------------------------------------------------
>
> Key: NIFI-2709
> URL: https://issues.apache.org/jira/browse/NIFI-2709
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.0.0
> Environment: Ubuntu 16.04 LTS with openjdk-8-jre-headless
> Reporter: Emil Frank
> Priority: Minor
> Attachments: screenshot-1.png
>
>
> When using the new ConsumeIMAP and ConsumePOP3 processors with a Microsoft
> Exchange 2013 IMAP server the flowfiles which are produced are simple HTML
> messages with no RFC2822 headers. I have also tried setting Exchange to force
> emails to be text only, sadly only the body with some Content-Type: fields
> are outputed.
> This mean that ExtractEmailHeaders and ExtractEmailAttachments cannot be used
> directly with these processors.
> In Python, I can force Exchange to output the headers by specify RFC822 in
> the connection settings:
> - https://docs.python.org/3/library/imaplib.html#imap4-example
> Is a similar option available for the spring mail framework?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
