[
https://issues.apache.org/jira/browse/NIFI-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391876#comment-15391876
]
ASF GitHub Bot commented on NIFI-1148:
--------------------------------------
Github user olegz commented on the issue:
https://github.com/apache/nifi/pull/710
@trixpan I can't say I am in favor of it given the fact that JavaMail
Properties is a distinct part of Java Mail API and there are quite a number of
them, so the question is how do you choose which once are more essential then
others and what should their default values be if exposed as top level
properties of a Processor? These are all tough questions to answer especially
in the early stages of the processor development when we didn't really have a
chance to analyze how it's been used and what are the common suggestions from
users.
So what I would propose is to add a note to CapabilityDescription that
"additional JavaMail properties should be set as Dynamic Properties". What do
you think?
> 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)
