[
https://issues.apache.org/jira/browse/NIFI-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15535864#comment-15535864
]
ASF GitHub Bot commented on NIFI-2709:
--------------------------------------
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/1083
@bbende this should solve the IMAP issue.
Notes:
1. This PR reads the content of the message into memory, in contrast with
the original design that relied on InputStream to write the content into the
FlowFile. This is due to the fact that JavaMail doesn't seem to have an
inputstream method capable of providing an RFC2822 message. In case anyone has
an idea on how to improve that, I am keen to incorporate into this PR.
2. The PR includes a GreenMail based junit and required dependency to ease
debugging. Since I am not sure if we want to refactor the jUnits already in
place (they seem to work well) with GreenMail based jUnits I aded very little
coverage. Let me know your preference and I will either remove the new jUnit or
to refactor @olegz original jUnit to use GreenMail based unit testing.
3. This will fail contrib-check. To be addressed once we decide what to do
with the jUnit tests mentioned above.
> 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
> Assignee: Andre
> 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)
