[GitHub] nifi issue #483: NIFI-1899 - Introduce ExtractEmailAttachments and ExtractEm...

2016-07-16 Thread trixpan
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/483 @JPercivall Fixing the rebase. Please hold --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[GitHub] nifi issue #483: NIFI-1899 - Introduce ExtractEmailAttachments and ExtractEm...

2016-07-16 Thread JPercivall
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/483 Thank you for the complements. The "InterruptedException" essentially means something want this thread to stop for some reason (here's an overview of

[GitHub] nifi issue #483: NIFI-1899 - Introduce ExtractEmailAttachments and ExtractEm...

2016-07-16 Thread trixpan
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/483 @JPercivall Beautiful code! Loved it. Interesting to see your programming thinking. Great lesson (specially because I tried to achieve a similar - though more covoluted - logic previously and failed.

[GitHub] nifi issue #483: NIFI-1899 - Introduce ExtractEmailAttachments and ExtractEm...

2016-07-13 Thread JPercivall
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/483 @trixpan do you by chance have a template that I can use to validate the processors with? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] nifi issue #483: NIFI-1899 - Introduce ExtractEmailAttachments and ExtractEm...

2016-07-11 Thread ijokarumawak
Github user ijokarumawak commented on the issue: https://github.com/apache/nifi/pull/483 @trixpan Exactly. "Having a single connection is enough" was my expected behavior, but it wasn't. The error doesn't happen all the time, but quit often, so I think it's a race condition. The

[GitHub] nifi issue #483: NIFI-1899 - Introduce ExtractEmailAttachments and ExtractEm...

2016-07-11 Thread trixpan
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/483 @ijokarumawak - thanks for looking at it. So just for me to confirm: PutEmail connects and tries to use SSL. This fails. It holds the socket PutEmail connects again with

[GitHub] nifi issue #483: NIFI-1899 - Introduce ExtractEmailAttachments and ExtractEm...

2016-07-11 Thread ijokarumawak
Github user ijokarumawak commented on the issue: https://github.com/apache/nifi/pull/483 @trixpan I am not sure 100% yet about the javax.mail.SocketFetcher's behavior, but I recommend to set higher value as default for `Maximum number of SMTP connection`, such as `1,000`, and

[GitHub] nifi issue #483: NIFI-1899 - Introduce ExtractEmailAttachments and ExtractEm...

2016-07-10 Thread trixpan
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/483 @ijokarumawak Still not clear to me how you are reaching the error. Also, note the QUIT message is not a requirement, a client may chose to send more than a message per session, example:

[GitHub] nifi issue #483: NIFI-1899 - Introduce ExtractEmailAttachments and ExtractEm...

2016-07-10 Thread ijokarumawak
Github user ijokarumawak commented on the issue: https://github.com/apache/nifi/pull/483 Looked at the SMTP server side, org.subethamail.smtp.server.SMTPServer to investigate how it uses maxConnections. It's used as a Semaphore. With successful transport, there's a QUIT message and

[GitHub] nifi issue #483: NIFI-1899 - Introduce ExtractEmailAttachments and ExtractEm...

2016-07-08 Thread JPercivall
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/483 The email-nar does not have a LICENSE or NOTICE in its src directory. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project