[
https://issues.apache.org/jira/browse/NIFI-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381059#comment-15381059
]
Dan Marshall commented on NIFI-1899:
------------------------------------
It's hard for me to tell if you folks are working on a single processor or
multiple.
I vote for a stand-alone "SMTP Listener" processor, then separate email parsing
processor(s). I have a system where we extended an open source project named
"Subethamail" ( https://github.com/voodoodyne/subethasmtp ) and added a Kafka
producer. I'd love to replace this with a NiFi "SMTP Listener" processor. It's
job would be to do the protocol exchange with the SMTP sender, grab the payload
("DATA") and offer as NiFi output stream.
In our app downstream we parse emails by reading the Kafka queue from Storm. We
would certainly look at replacing this with an email parser NiFi processor -
but that would be difficult due to the complexity already in place.
However, we could very easily plug in an SMTP Listener processor.
> Create ListenSMTP & ExtractEmailAttachment processors
> -----------------------------------------------------
>
> Key: NIFI-1899
> URL: https://issues.apache.org/jira/browse/NIFI-1899
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Andre
> Fix For: 1.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
