Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 07-22-2022 07:19 AM
After following this article, I tried to create a flow where email attachments, subject, body, to, from, cc, bcc etc. can be extracted.
However the flow is not proceeding beyond the first processor:
ConsumeIMAP is showing 0(0 bytes) in its Out, as shown in screenshot above.
Created 07-26-2022 12:31 AM
My problem was solved after using a different email id.
As far as gmail settings are concerned:
Created 07-22-2022 07:24 AM
@sayak17 Do you have connectivity to port 993 from nifi host to gmail host? Test this with telnet to ensure network is connecting. If not, check nifi host firewall, etc. After this if still cannot connect, there may be gmail settings you need to enable to allow connectivity.
Created 07-22-2022 07:43 AM
@steven-matison I am unable to activate telnet on my windows. It is stuck:
Any other way to check? Also is it possible to use a different port in the nifi processor's configuration and make it work?
Created 07-22-2022 07:50 AM
In windows are you able to connect to gmail/imap using email client? Assuming nifi is on windows, that may be a test. I still think there are things needing to do on gmail side to allow.
The imap port needs to be whatever port gmail provides. I assume it is 993 from above. Another port will not resolve connectivity issue, unless 993 is the wrong port alltogether.
Created 07-22-2022 08:02 AM
Yes, I am able to connect to gmail using outlook. Yes nifi is on windows.
I had already enabled 'less secure app access' on gmail.
I had used 993 port, because that's what the article I have linked in my question had used. Googling around, I see 993 is the port used for IMAP.
Created 07-26-2022 12:31 AM
My problem was solved after using a different email id.
As far as gmail settings are concerned: