[ 
https://issues.apache.org/jira/browse/NIFI-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542182#comment-15542182
 ] 

ASF GitHub Bot commented on NIFI-2709:
--------------------------------------

Github user trixpan commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/1083#discussion_r81531370
  
    --- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/java/org/apache/nifi/processors/email/AbstractEmailProcessor.java
 ---
    @@ -348,14 +345,11 @@ private void transfer(Message emailMessage, 
ProcessContext context, ProcessSessi
             long start = System.nanoTime();
             FlowFile flowFile = processSession.create();
     
    -        flowFile = processSession.append(flowFile, new 
OutputStreamCallback() {
    -            @Override
    -            public void process(final OutputStream out) throws IOException 
{
    -                try {
    -                    StreamUtils.copy(emailMessage.getInputStream(), out);
    -                } catch (MessagingException e) {
    -                    throw new IOException(e);
    -                }
    +        flowFile = processSession.append(flowFile, out -> {
    --- End diff --
    
    having said that, if necessary, happy to try to avoid using the lambda


> 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: 1083.patch, 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)

Reply via email to