Dan, Ingesting Microsoft Journals seem like a great suggestion for a new processor ( ParseExchangeJounal ?).
Regarding TNEF: As far as I know, Apache Commons - Mail does not pase "winmail.dat" type attachments. As far as I understand the only ASL compatible implementation of a TNEF extractor is Apache's POI and even that implementation is not part of POI's main release. If TNEF support is required we will ether have to code from scratch or perhaps use https://github.com/koodaamo/tnefparse together with ExecuteScript (although since tnefparse is LGPL, this solution cannot be packaged as part of NiFi). Cheers On Sun, Jul 17, 2016 at 10:53 AM, djmdata <danmarshal...@gmail.com> wrote: > What is the JIRA #? > > I have a production system that reads email from a custom SMTP listener and > places the SMTP payload into Kafka. A Storm topology reads messages from > Kafka and parses the emails (Java code using JavaMail API) into useful info > (subject, text, attachments, body, etc...). > > I'm looking at plugging NiFi into this to replace the custom SMTP listener. > If you had a processor that could act as a reliable (we can't lose emails) > and performant SMTP listener alternative we would use it. > > Your "email parser processor" is an interesting idea - but beware of the > mess you'll find in the wild with email. In our case, we try to parse > Exchange (full of non-standard wonders like "TNEF" attachments") as well as > email from virtually anywhere (GMail, Yahoo, Joe's email client...). If you > can crack that you'll be on to something. We have even more complexity in > that we read "Microsoft Journals" which wrap the standard SMTP layout in a > Microsoft layer (you'll see this at large Exchange shops doing this kind of > thing for use cases like compliance). > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/ListenSMTP-processor-tp10510p12827.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >
