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

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

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

    https://github.com/apache/nifi/pull/710#discussion_r73805385
  
    --- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/resources/docs/org.apache.nifi.processors.email.ConsumeIMAP/additionalDetails.html
 ---
    @@ -0,0 +1,60 @@
    +<!DOCTYPE html>
    +<html lang="en">
    +<!--
    +      Licensed to the Apache Software Foundation (ASF) under one or more
    +      contributor license agreements.  See the NOTICE file distributed with
    +      this work for additional information regarding copyright ownership.
    +      The ASF licenses this file to You under the Apache License, Version 
2.0
    +      (the "License"); you may not use this file except in compliance with
    +      the License.  You may obtain a copy of the License at
    +          http://www.apache.org/licenses/LICENSE-2.0
    +      Unless required by applicable law or agreed to in writing, software
    +      distributed under the License is distributed on an "AS IS" BASIS,
    +      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 
implied.
    +      See the License for the specific language governing permissions and
    +      limitations under the License.
    +    -->
    +<head>
    +<meta charset="utf-8" />
    +<title>ConsumeIMAP</title>
    +<link rel="stylesheet" href="../../css/component-usage.css"
    +   type="text/css" />
    +</head>
    +
    +<body>
    +   <!-- Processor Documentation 
================================================== -->
    +   <h2>Description:</h2>
    +   <p>This Processors consumes email messages via IMAP protocol and
    +           sends the content of an email message as content of the 
FlowFile.
    +           Content of the incoming email message is written as raw bytes 
to the
    +           content of the outgoing Flow File.
    +    </p>
    +
    +   <p>Since different serves may require different Java Mail
    +           properties such properties could be provided via dynamic 
properties.
    +           For example, below is a sample configuration for GMail:
    +   </p>
    +   <p>
    +           <b>Processor's static properties:</b>
    +           <ul>
    +                   <li><b>Host Name</b> - imap.gmail.com</li>
    +                   <li><b>Port</b> - 993</li>
    +                   <li><b>User Name</b> - <i>[your user name]</i></li>
    +                   <li><b>Password</b> - <i>[your password]</i></li>
    +                   <li><b>Folder</b> - INBOX</li>
    +           </ul>
    +           <b>Processor's dynamic properties:</b>
    +           <ul>
    +                   <li><b>mail.imap.socketFactory.class</b> - 
javax.net.ssl.SSLSocketFactory</li>
    +                   <li><b>mail.imap.socketFactory.fallback</b> - false</li>
    +                   <li><b>mail.store.protocol</b> - imaps</li>
    --- End diff --
    
    Unfortunately we can't do that, for reasons that there are no sensible 
defaults for protocols, only for providers. So if we ever get to something like 
ConsumeGmailViaIMAP, then we could eliminate most of not all dynamic 
properties, but unless we get into provider specific processors we have to stay 
pure to protocols and APIs.


> Add processor to GetEmail supporting IMAP and POP3
> --------------------------------------------------
>
>                 Key: NIFI-1148
>                 URL: https://issues.apache.org/jira/browse/NIFI-1148
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Joseph Witt
>            Assignee: Oleg Zhurakousky
>             Fix For: 1.0.0
>
>
> It is fairly common that users want to be able to acquire data via email.  
> This means both IMAP and POP3.  POP3 is easier as it is a sort of fire/forget 
> model whereas IMAP involves more state handling.  But in any event both modes 
> are important to support.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to