[
https://issues.apache.org/jira/browse/NIFI-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409587#comment-15409587
]
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_r73712664
--- Diff:
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/java/org/apache/nifi/processors/email/ConsumeIMAP.java
---
@@ -0,0 +1,91 @@
+/*
+ * 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.
+ */
+package org.apache.nifi.processors.email;
+
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.List;
+
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.springframework.integration.mail.ImapMailReceiver;
+
+@InputRequirement(Requirement.INPUT_FORBIDDEN)
+@CapabilityDescription("Consumes messages from Email Server using IMAP
protocol. "
+ + "The raw-bytes of each received email message are written as
contents of the FlowFile")
+@Tags({ "Email", "Imap", "Get", "Ingest", "Ingress", "Message", "Consume"
})
+public class ConsumeIMAP extends AbstractEmailProcessor<ImapMailReceiver> {
+
+ public static final PropertyDescriptor SHOULD_MARK_READ = new
PropertyDescriptor.Builder()
+ .name("Mark Messages as Read")
+ .description("Specify if messages should be marked as read
after retrieval.")
+ .required(true)
+ .allowableValues("true", "false")
+ .defaultValue("false")
+ .addValidator(StandardValidators.BOOLEAN_VALIDATOR)
+ .build();
+ public static final PropertyDescriptor USE_SSL = new
PropertyDescriptor.Builder()
+ .name("Use SSL")
+ .description("Specifies if IMAP connection must be obtained
via SSL encypted connection (i.e., IMAPS)")
--- End diff --
@mattyb149 Actually you're not missing anything and there is no extra
configuration on the cline side (NIFI). This is all derived form the email
server capabilities and how it's configured. For example if you want to test it
with your existing GMail you would have to use "imaps". That is because Google
has set it up as such. Does that help?
> 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)
